Agents show active in the AWI but they are not connected.
search cancel

Agents show active in the AWI but they are not connected.

book

Article ID: 387301

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Agents show active in the AWI but they are not connected.

The JCP(s) create forced traces with these messages:

20241211/192016.404 - 1022             ----------------------- Stack Trace -----------------------
20241211/192016.404 - 1022             java.util.ConcurrentModificationException
20241211/192016.404 - 1022                 at java.base/java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1013)
20241211/192016.404 - 1022                 at java.base/java.util.ArrayList$Itr.next(ArrayList.java:967)
20241211/192016.404 - 1022                 at com.automic.agents.impl.DuplicateAgents.checkTimeout(DuplicateAgents.java:83)
20241211/192016.404 - 1022                 at com.automic.agents.impl.DuplicateAgents$1.run(DuplicateAgents.java:71)
20241211/192016.404 - 1022                 at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
20241211/192016.404 - 1022                 at java.base/java.util.TimerThread.run(Timer.java:516)
20241211/192016.405 - 1022             
20241211/192016.405 - 1022             --------- Location from where the trace was called --------
20241211/192016.405 - 1022             com.automic.util.logging.impl.CallStackException
20241211/192016.405 - 1022                 at com.automic.util.logging.impl.ForcedTrace.writeDump(ForcedTrace.java:62)
20241211/192016.405 - 1022                 at com.automic.util.logging.impl.LogComponent.logError(LogComponent.java:478)
20241211/192016.405 - 1022                 at com.automic.kernel.impl.DefaultExceptionHandler.uncaughtException(DefaultExceptionHandler.java:39)
20241211/192016.405 - 1022                 at com.automic.kernel.impl.DefaultExceptionHandler.uncaughtException(DefaultExceptionHandler.java:21)
20241211/192016.405 - 1022                 at java.base/java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1082)
20241211/192016.405 - 1022                 at java.base/java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1077)
20241211/192016.405 - 1022                 at java.base/java.lang.Thread.dispatchUncaughtException(Thread.java:2008)

The JCP logs show these messages:

20241210/111018.196 - 1      U00003486 ListenSocket with port number '58324' successfully created.
20241210/111018.234 - 1      U00003488 Server 'JCP server_name IP address ' was started as instance '9'.
20241210/111018.277 - 1      U00045474 Create acknowledgement for undeliverable message 'FTXINF(63)' (bacv '613619431') to 'null'.
20241210/111018.286 - 1      U00045474 Create acknowledgement for undeliverable message 'FTXINF(63)' (bacv '613619432') to 'null'.
20241210/111018.294 - 1      U00045474 Create acknowledgement for undeliverable message 'FTXINF(63)' (bacv '613619433') to 'null'.

 

Environment

Automic Automation Engine 21.0.X, 24.X

Cause

Defect.

Resolution

A problem has been fixed where the agent connection will be re-established in case of a duplicate connection that happened during a JCP disconnect to the agent.

Component: Automation Engine, Agent Unix

Automation Engine 21.0.13 - Available

Automation Engine 24.3.0 HF2 - Available

 

Additional Information

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

Article title: How to register to Broadcom Software Product updates and Critical Alerts

https://knowledge.broadcom.com/external/article?articleId=133819

Defect ID: DE157241