JDE RA agent having version 2.2.8 closing connection after being idle for some time.

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

After upgrading the Automic Automation Engine to version 24.4 and the JDE RA Agent to version 2.2.8, the agent loses connectivity to the JDE job table after sitting idle for an extended period (typically a couple of days).

Symptoms:

• Job statuses become unreachable.

• The RA Core 24.4.1 reports a failure but does not re-establish the connection, continuing to poll without success.

• Restarting the agent temporarily resolves the issue, allowing it to find the ending status and update accordingly.

Error Messages: The following errors are observed in the JDE trace logs (Ra_trace_00.txt):

JDE-Error:Invalid state, the Connection object is closed. Status Monitor: JDEdwardsAgentImpl: return Connection:, was closed

Environment

Automic Automation V 24.4.x

RA JDE core: V 24.4.x

JDE agent software version: 2.2.8

 

Cause

This issue has been identified as a defect (DE177234) related to differences in Java versions between RA Core releases.

• RA Core 21.0.9 utilized Java 8, which did not close inactive connections, allowing the agent to self-recover if a disconnect occurred.
• RA Core 24.4.1 utilizes Java 17. Java 17 appears to close idle connections after a certain period. The current implementation of the RA Core 24.4.1 does not successfully reconnect after this closure occurs.

Resolution

Workaround:

Until a fix is provided in a future release, the following workarounds are available:

Restart the Agent: Manually restarting the JDE RA Agent will re-establish the connection and update job statuses.

Downgrade RA Core: If feasible, utilize RA Core version 21.0.9 (which uses Java 8) while investigating, as it is known to self-recover from these disconnects