Changing expired password results in error message "AwE-5009 RMI connection failure, check if RmiServer is running"

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When a User's password is expired, the user is prompted to enter a new password after attempting to log in. 

After entering the new password and selecting OK, the error message "AwE-5009 RMI connection failure, check if RmiServer is running" is seen. 

Error details show the following error:

java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
 at java.base/java.net.PlainSocketImpl.connect0(Native Method)
 at java.base/java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:101)
 at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
 at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)
 at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224)
 at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
 at java.base/java.net.Socket.connect(Socket.java:608)

The password does not get changed and the User is unable to log in. This occurs only with the following configuration:

• The port ClientRMIPortNumber is defined the Options.properties file (only defined if active firewall is in place)
• Applications Manager version 9.3.x

While all version of 9.3.x should be affected, the issue has been reproduced in version 9.3.4 and 9.3.5

In Applications Manager version 9.3.x and with an active firewall in place, the Client RMI Port Number has to be defined and used as the local client port. 

This is defined in the Options.properties file. When 

Environment

Release : 9.3.x

Component : APPLICATIONS MANAGER

Cause

When attempting to update password, the client is likely attempting to open a new connection using the same ClientRMIPortNumber on top of the already established connection which is using the same port.

Resolution

This is fixed in version 9.4.x and higher

Workarounds:

• Users need manually update their password before password expiration
• Another User with User edit permissions can update the password (ie sqloper user)
• Set password to not expire