Agent is not running on multinode environment
SummaryOn production environment, agent appears to be running in SMA, but the timestamp is not getting updated. And cases are not getting created.
Error Messages"RMI TCP Connection(16870)-XXXXXXXXXXXXX" Id=7390 in BLOCKED on lock=com.pega.pegarules.session.internal.async.AgentQueue@4285c3ee owned by RMI TCP Connection(16869)-XXXXXXXXXXXX Id=7405BlockedCount : 1, BlockedTime : -1, WaitedCount : 14, WaitedTime : -1 at com.pega.pegarules.session.internal.async.AgentQueue.restart(AgentQueue.java:701) at com.pega.pegarules.session.internal.async.Agent.restartQueue(Agent.java:1091) at com.pega.pegarules.management.internal.AgentManagementAPI.Start(AgentManagementAPI.java:245) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606)
Steps to ReproduceNot Applicable
Root CauseA defect in Pegasystems’ code or rules the thread which was trying to restart the agent got blocked and since it was holding lock on AgentQueue, other threads went stalled, waiting for the agent thread to complete
ResolutionIncrease the thread pool size.The behavior is generic to threads being blocked which happens intermittently, however to handle the agent Mutual exclusivity there is a user story created which is scheduled to be implemented in Pega 7.2.2.
For time being on Pega 7.2 increased thread pool size would suffice.
Published July 19, 2016 - Updated August 11, 2016