JWP's Can't connect - Error: Cannot assign requested address: connect

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Java work process (JWP) fails to connect with the following error:

20200611/081105.758 - 55     U00003303 Could not establish a connection to Server 'NONPROD#WP002' (IP address: '10.80.220.131', Port: '0').
20200611/081105.758 - 55     U00045014 Exception 'java.net.BindException: "Cannot assign requested address: connect"' at 'sun.nio.ch.Net.connect0()'.
20200611/081205.805 - 53     U00003490 Connection to 'Host' initiated, client connection '9'
20200611/081205.807 - 53     U00003303 Could not establish a connection to Server 'NONPROD#WP002' (IP address: '10.80.220.131', Port: '0').
20200611/081205.809 - 53     U00045014 Exception 'java.net.BindException: "Cannot assign requested address: connect"' at 'sun.nio.ch.Net.connect0()'.

Environment

Release : 12.0.X, 12.1.X, 12.2.X, 12.3.X

Component : AAUTEN

Cause

In this special circumstance, the primary work process (PWP) hangs which block the Java work process (JWP) connection causing the failure 

Resolution

Restart the primary work process (PWP)

Additional Information

We have seen cases in a multiple server/failover type of setting when the server where you are wanting to failover _to_ (we'll call this server B) is started before the server you are failing over _from_ (we'll call this server A) has stopped completely and the PWP is not started, but it has not fully stopped. In this case, a PWP on server B will never start and the CPs on server B are trying to connect to the PWP on server A. 

Make sure that processes on server A (in the situation defined above) are completely stopped before starting the processes on server B.