Automatic Deployment Engine returns error (80) session error, Unable to open a client session for <hostname>:48000: Connection refused: connect

Document ID : KB000034980
Last Modified Date : 07/02/2019
Show Technical Document Details
Issue:
When deploying a new Robot using Automatic Deployment Engine ADE
You might receive the following error:
apr 18 19:26:20:950 [pool-2-thread-1, automated_deployment_engine] try to open socket for xxxxxxxxx01:48000
apr 18 19:26:20:950 [pool-2-thread-1, automated_deployment_engine] createSocket: host=xxxxxxxxxxx port=48000 localBindAddress=/<ip_address> localBindPort=0
04182014 19:26:41,953 [pool-2-thread-1] ERROR AbstractDeploymentStrategy - Error encountered during command CheckRobotPostprocess: Unable to open a client session for xxxxxxxxxxx:48000
04182014 19:26:41,954 [pool-2-thread-1] INFO AbstractDeploymentStrategy - Executing rollback.
04182014 19:26:41,954 [pool-2-thread-1] INFO AbstractActor - Deployment of 'robot_exe' finished
04182014 19:26:41,957 [pool-2-thread-1] FATAL AbstractActor - Error encountered during distribution of robot_exe.zip to target xxxxxxxxxxx: (4,Install Failure)
com.nimsoft.ADE.core.DeploymentException: (80) Session error, Unable to open a client session for xxxxxxxxxxx:48000: Connection refused: connect
at com.nimsoft.ADE.actor.HostActor.install(HostActor.java:39)
at com.nimsoft.ADE.actor.HostActor.install(HostActor.java:19)
at com.nimsoft.ADE.actor.AbstractActor.run(AbstractActor.java:73)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: (80) Session error, Unable to open a client session for xxxxxxxxxxx:48000: Connection refused: connect

After deployment ADE is trying to verify that the robot is up and running by connecting to port 48000 for the controller and failing.
Resolution:
The Automatic Deployment Engine has a setting that can be changed to allow for a delay before testing if the robot is up and running.

This can be set in automated_deployment_engine.cfg like this :

<automated_deployment_engine>
verify_delay = 200
</automated_deployment_engine>

This should be done on the Automatic Deployment Engine deploying the robot.