Only one client session can be opened to the same Master on the same Machine by default.

Document ID : KB000088279
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Only one client session can be opened for the same Automation Engine (Master) on the same Machine by default.

Error Message Details:
AwE-5009 RMI connection failure, check if RmiServer is running

Details:
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.Socket.bind(Unknown Source)
at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.bind(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(Unknown Source)
at com.appworx.client.screen.util.ClientSocketManager.A(ClientSocketManager.java:241)
at com.appworx.client.screen.util.ClientSocketManager.connect(ClientSocketManager.java:307)
at com.appworx.client.screen.util.Loader.setMaster(Loader.java:941)
at com.appworx.client.screen.logon.C.Þ(Logon.java:228)
at com.appworx.client.screen.main.AxMain.A(AxMain.java:2209)
at com.appworx.client.screen.main.AxMain.main(AxMain.java:2849)
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 com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
 
Symptoms
In Applications Manager only one client session can be opened to the same Master on the same machine by default.  If an attempt is made to try and open more than one client session, you will receive the above error.

Cause
With TCP/
IP you cannot have 2 sockets connected with the same parameters. Therefore, if you have a firewall installed and have the ClientRMIPortNumber (defined in the Options.properties file) locked down to a single port only one client session is allowed.



 
Resolution:
If the RmiServer is behind a firewall only the RMIRegistryPortNumber and the RMIDataPortNumber (specified in the Options.properties file) need to be open in the RmiServer's firewall (defaults to 1099). 

Remove the ClientRMIPortNumber from the Options.properties file, if it exists, or set it to 0 to allow more than one client session to be opened. 

Reference

For more information pertaining to these settings, see the Applications Manager documentation:


Installation Guide > CA Automic Applications Manager Installation--Advanced Topics > Automation Engine, Agent, and Client Firewall Connections