Java Web Client fails to Launch or Login with error "Connection refused: connect"
search cancel

Java Web Client fails to Launch or Login with error "Connection refused: connect"


Article ID: 95909


Updated On:


CA Automic Applications Manager (AM)


Launching the Java Web Client results in the error "AwE-5009 - RMI connection failure,check if Rmi server is running".

Selecting details button show the error " Connection refused: connect".

The RmiServer is running with no errors appearing in RMI logs. Below is the full error: Connection refused: connect
    at Method)
    at Source)
    at Source)
    at Source)
    at Source)
    at Source)
    at Source)
    at<init>(Unknown Source)
    at Source)
    at com.appworx.client.screen.util.ClientSocketManager.A(
    at com.appworx.client.screen.util.ClientSocketManager.connect(
    at com.appworx.client.screen.util.Loader.setMaster(
    at com.appworx.client.screen.logon.C.Ń(
    at com.appworx.client.screen.main.AxMain.A(
    at com.appworx.client.screen.main.AxMain.main(
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.sun.javaws.Launcher.executeApplication(Unknown Source)
    at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
    at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
    at Source)
    at Source)


Component: APPMGR


9.2.x or below:

There is an issue with the connection from the user's PC to the master

9.3.x or above:

Apache service may be stopped


Correct any connection issues by enabling client debug and reviewing the Java console logs created during Java Web Client startup process.

Possible connection issues can occur for the following reasons:

9.2.x or below:

  • Incorrect RMIHostID value in the $AW_HOME/web/classes/ or %AW_HOME%/web/classes/ (Windows OS)
  • Incorrect RMIRegistryPortNumber $AW_HOME/web/classes/ %AW_HOME%/web/classes/ (Windows OS)
  • Firewall between the User's PC and RMIHostID (make sure you can connect to the master's RMIHostID and RMIRegistryPortNumber using telnet or similar command)

9.3.x or above:

  • Check to see if Apache is up and running. If Apache is stopped, start Apache processes

Additional Information

Client debug can be enabled by following the below procedures:

9.2.x or below:

1. Edit the $AW_HOME/web/Client.jnlp or %AW_HOME%\web\Client.jnlp (Windows OS). Change the below line and save.

<property name="jnlp.appworx.debug" value="false"/>

<property name="jnlp.appworx.debug" value="true"/>  

2. Open Java control Panel > Select Advanced Tab > Enable tracing, logging, and show console options > Apply.

3. Clear Java cache from from Java Control Panel by selecting > General Tab > Temporary Internet Files Settings > Delete Files > Check all available options > Select OK.

4. Launch New Java Web Client session from Web Browser. A Java console windows should appear and provide additional debug information regarding the Java Web Client session.

9.3.x or above:

Debug information can be found in the online documentation topic Opening the Applications Manager Client and Logging In