JWP can't connect to the CPs | Connection refused
Article ID: 112289
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
The JWP (Java Work Process) can't connect to the running CPs (Communications Processes) when multiple network addresses are available on the Host and the parameter bindaddr and hostname is set and used in the ucsrv.ini.
The following error can be found in the logfile of the JWP processes for all available CPs:
U00003303 Could not establish a connection to Server AUTOMIC#CP001' (IP address: 192.0.2.1', Port: '2217').
U00045014 Exception 'java.net.ConnectException: "Connection refused"' at 'sun.nio.ch.Net.connect0()'.
U00003303 Could not establish a connection to Server AUTOMIC#CP002' (IP address: 192.0.2.1', Port: '2218').
U00045014 Exception 'java.net.ConnectException: "Connection refused"' at 'sun.nio.ch.Net.connect0()'.
U00003303 Could not establish a connection to Server AUTOMIC#CP003' (IP address: 192.0.2.1', Port: '2219').
U00045014 Exception 'java.net.ConnectException: "Connection refused"' at 'sun.nio.ch.Net.connect0()'.
U00003303 Could not establish a connection to Server AUTOMIC#CP004' (IP address: 192.0.2.1', Port: '2220').
U00045014 Exception 'java.net.ConnectException: "Connection refused"' at 'sun.nio.ch.Net.connect0()'.
Environment
N/A
Cause
The JWP can not connect to the hostname which was by error available for the Communication processes in the MQSRV table (MQSRV_TcpIpAddr). In the second available IP address column (MQSRV_TcpIpAddr2) a wrong address was available. Therefore the JWP was not able to connect to the CPs.
As a recommendation, in the ucsrv.ini file only the value for "bindaddr" or "hostname" should be used.
If a value for bindaddr is configured, all processes will register in the database only with the IP address specified in bindaddr.
The value for hostname will be ignored in this case.
If the value for "hostname" is configured, the processes will register in the database with the hostname and the listen socket will be started an all IP addresses.
As a recommendation, in the ucsrv.ini file only the value for "bindaddr" or "hostname" should be used.
If a value for bindaddr is configured, all processes will register in the database only with the IP address specified in bindaddr.
The value for hostname will be ignored in this case.
If the value for "hostname" is configured, the processes will register in the database with the hostname and the listen socket will be started an all IP addresses.
Resolution
The reported issue has been fixed with an internal bug fix.
Please upgrade to one of the below mentioned versions which includes the fix or a higher one if available.
Component(s):
Automation Engine
Fix Version(s):
Automation.Engine 12.1.3 - already released
Automation.Engine 12.2.0 - already released
Please upgrade to one of the below mentioned versions which includes the fix or a higher one if available.
Component(s):
Automation Engine
Fix Version(s):
Automation.Engine 12.1.3 - already released
Automation.Engine 12.2.0 - already released
Additional Information
As a workaround, to correct the wrong entries in the MQsrv, the following can be tried:
1. Comment the value for the hostname in ucsrv.ini file and set the value for only bindaddr.
2. Then do a CP restart (or start an additional CP).
3. Check afterward the values in the MQSRV table.
4. The column MQSRV_TcpIpAddr and MQSRV_TcpIpAddr2 should have the correct IP address.
5. Then restart all CP processes one after the other and check once again that the values in MQSRV are correct (only IPs) are used.
6. In the end, restart all JWP and JCP processes, and check in the log files that they are connected to the right IP addresses.
7. Verify that there are no connections to the wrong address.
1. Comment the value for the hostname in ucsrv.ini file and set the value for only bindaddr.
2. Then do a CP restart (or start an additional CP).
3. Check afterward the values in the MQSRV table.
4. The column MQSRV_TcpIpAddr and MQSRV_TcpIpAddr2 should have the correct IP address.
5. Then restart all CP processes one after the other and check once again that the values in MQSRV are correct (only IPs) are used.
6. In the end, restart all JWP and JCP processes, and check in the log files that they are connected to the right IP addresses.
7. Verify that there are no connections to the wrong address.
Feedback
Yes
No
Powered by
