ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Automic JCP does utilize the timeout setting in the ucsrv.ini


Article ID: 143237


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine


During periods of network interruption, the JCP does not properly register a timeout as set in the aliveTimeout section of the configuration file ucsrv.ini.


Release : 12.2



A problem has been fixed where the parameter aliveTimeout in ucsrv.ini was ignored if the server is a REST API.

The parameter [TCP/IP]/aliveTimeout in ucsrv.ini can be used to define an interval in which the TCP/IP connection to other server processes are checked.

This functionality was not implemented in JCP(REST API).

If there is a network problem between a JCP and WPs it is possible that the JCP does not detected the IO error.

Then the REST API produces many log messages with the number U00003339 and the processing of REST calls may be much slower.

Restarting the JCP solves the problem until the next network interruption happens.