Java Web Client Login Failure: "Connection refused: connect" - Automic Applications Manager

Products

• Automic Applications Manager

Issue/Introduction

When launching or logging into the Automic Applications Manager Java Web Client, the connection fails with an "AwE-5009 - RMI connection failure" or "AwE-9999 Internal error" message. Selecting the details button reveals the following Java connection exception: java.net.ConnectException: Connection refused: connect

This issue occurs when the client machine is unable to successfully establish a socket connection to the master server’s IP and port, preventing the application from initializing.

Environment

Applications Manager 9.4 and above

Cause

The java.net.ConnectException: Connection refused: connect error indicates that the Java Client cannot establish a TCP/IP connection to the master server. This is typically caused by:

• Firewall rules blocking the communication port between the client and master.
• Network routing or VPN issues preventing access to the master server’s IP.
• The required webserver (Apache/Tomcat) process being stopped on the master server.

Resolution

1. Verify the master server status: Ensure the webserver is active and running on the master server.
2. Test network connectivity: From the client machine, run the following PowerShell command to verify if the server IP and port are reachable: Test-NetConnection -ComputerName [Master_IP] -Port [RMI Registry Port_Number]
3. Check firewall rules: If the connection test fails, verify that your network firewall allows traffic from your IP to the master server on the designated RMI and webserver ports.
4. Review configurations: Check the $AW_HOME/web/classes/Options.properties file to ensure the RMIHostID and RMIRegistryPortNumber are correctly set for your environment.