System will not work on JWP startup - >libcpprnt/src/Channel.cpp#sys::Channel::write:72<'.

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

Some Automic functionality stops working when JWPs are started up.  The functionality could be many things including, but not limited to:

Call Notifications objects are failing intermittently
Users are unable to login
General performance issues

The setup of the automation engine components matches:

More than one server with AE components on it
AE components are on windows
WP log files show something like:

U00003102 Unable to connect client 'AUTOMIC#WP007/{IP address}({servername}):{port}', reason: '10057 - A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. >libcpprnt/src/Channel.cpp#sys::Channel::write:72<'.

Environment

More than one server with AE components on it
AE components are on windows
AE version 24.1.0 or 24.2.0

Cause

Defect where WPs on one server are unable to connect to the JWPs on another

Resolution

Solution:

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automation Engine
Automation.Engine 21.0.12 HF1 - Available
Will be fixed in Automation.Engine 21.0.13 - Planned release beginning March 2025
Will be fixed in Automation.Engine 24.3.0 - Planned release beginning December 2024

Workaround:

Some customer have seen a workaround of running more JWPs on each server (at least 4), with two of these JWPs per server having explicit roles set on startup: one as -role=AUT and one as -role=IDX.  

This can be implemented on a system where JWPs are started by service manager by opening the service manager dialog and for each server running JWPs and following the below steps:

1. Duplicate the current JWP entry four times - rename these as you'd like
2. Open one of the duplicated JWP entries and update the start command to include the parameter -role=IDX before the -svc%port% like the following:
   java -Xrs -Xmx2G -jar ucsrvjp.jar -IC:\automic\AutomationEngine\bin\ucsrv.ini -role=IDX -svc%port%
   
   
3. Open another of the duplicated JWP entries and update the start command to include the parameter -role=AUT before the -svc%port% like the following:
   java -Xrs -Xmx2G -jar ucsrvjp.jar -IC:\automic\AutomationEngine\bin\ucsrv.ini -role=AUT -svc%port%
   
   
4. The other 2 JWPs do not have to have a specified role (although this can be done if needed)

More information on setting roles can be found here: JWP Roles 

Additional Information

Defect ID: DE153431

Public Description: A problem has been fixed where Call Notification objects failed intermittently. 
This problem could occur if the Automation Engine was running on multiple Windows hosts.
Another symptom could be that JWP on a second windows node can not be started.