Java Web Client fails to launch with error message "AwE-5009 RMI connection failure, check if RmiServer is running"


Article ID: 87935


Updated On:


CA Automic Applications Manager (AM)


Error Message :
AwE-5009 RMI connection failure, check if RmiServer is running
details: null Address already in use: connect

An "AwE-5009 RMI connection failure, check if RmiServer is running" error message when failing to launch Java Web Client can occur for a number of reasons, and reviewing the "Details" of the error message can assist in determining where the issue is coming from.


The below error, specifically "Address already in use: connect" indicates that the error is on the client PC, not the Applications Manager server. Address already in use: 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)



Cause type:
Root Cause: Client machine has a "stuck" process that is using the IP/Port required by the Java Client.


OS: Windows
OS Version: N/A


  1. Check to see if there are any stuck Java processes on the client machine.  If there are then:
  • Kill the hung process
  • Re-launch the Java Web Client 
  1. If no processes are found: 
  • Restart the client machine.

Fix Status: No Fix

Fix Version(s):

Additional Information

Workaround :