search cancel

Java Agents cannot reconnect to AE - java.io.IOException: Too many open files

book

Article ID: 253144

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

After a deconnection of the JCP, the Java Based Agents (Agent JMX, Agent PeopleSoft, Agent RA Core, Agent SAP, Agent SQL, Analytics.Backend) have a file descriptor leak, as they don't handle well the deconnection to the JCP.

This causes that the process will have is thread count increased (this can be check with a ps command of lsof), and can lead to reach the user limit for this setting.

Example of error in the Agent log:

20220831/044035.198 - 1      com.uc4.ex.cp.InitialConnectionException: Initial connection with endpoint not possible. Please check your configuration.
20220831/044035.199 - 1      U02000379 Initiating connection to server 'AE:443' using WebSocket URI: 'wss://AE:443/agent'.
20220831/044035.212 - 1      java.io.IOException: Too many open files

Environment

Release : 21.0.x

Component(s): Agent JMX, Agent PeopleSoft, Agent RA Core, Agent SAP, Agent SQL, Analytics.Backend

Cause

Defect: failed connection attempts to the JCP resulted in a connection-leak.

Resolution

Workaround:

In order to avoid the agent being unable to connect to the JCP, please increase the maximum open file limits for the user start the agent (by default on Linux is 1024).

This can be increased either in the .profile (not recommended) of the user or in the /etc/security/limits.conf with this kind of lines (replacing USER by the one starting the Agent):

USER soft nofile 4096
USER hard nofile 8192

Solution:


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

Fix version:
Component(s): Agent JMX, Agent PeopleSoft, Agent RA Core, Agent SAP, Agent SQL, Analytics.Backend

Will be fixed on Automation.Engine 21.0.4 HF1
Will be fixed in Automation.Engine 21.0.5 - Planned release February 2023