Support Article
Not executing Resource Adapter function: RECENTS_DAEMON
SA-36521
Summary
Agents are not running properly and facing slowness issue in the environment. When checking the logs , getting below errors.
Error Messages
ERROR - invoke(): Node ID not found in request: RECENTS_DAEMON / RecentsDaemon
22:51:48,375 INFO [stdout] (Dispatcher-Thread-165) 2017-03-28 22:51:48,375 [-threads-2071895720)] [ STANDARD] [ PegaDM:07.10] ( etier.impl.AsyncServant) ERROR - invoke(): Node ID not found in request: RECENTS_DAEMON / RecentsDaemon
22:52:11,530 INFO [stdout] (Dispatcher-Thread-165) 2017-03-28 22:52:11,529 [-threads-2071895720)] [ STANDARD] [ PegaDM:07.10] ( internal.async.Agent) INFO - System date: Tue Mar 28 22:52:11 EST 2017 Total memory: 4,084,596,736 Free memory: 920,102,024 Requestor Count: 41 Shared Pages memory usage: 0%
22:52:12,071 INFO [stdout] (Dispatcher-Thread-165) 2017-03-28 22:52:12,056 [-threads-2071895720)] [ STANDARD] [ PegaDM:07.10] ( external.async.AbstractDaemon) ERROR - RecentsDaemon exiting with exception:
22:52:12,071 INFO [stdout] (Dispatcher-Thread-165) com.pega.pegarules.pub.PRException: Failed to execute Resource Adapter function: RECENTS_DAEMON {NodeID=94bd261d056b40a1cdfe7ce1d1114ee3, ExecutionDelay=4, ClientID=RecentsDaemon}
Steps to Reproduce
Not Applicable
Root Cause
An issue in the custom application code or rules where hornetQ in Jboss server delaying the message queue which resulting the agent to run slow after sometime.
Messages sent to HornetQ do not invoke the Pega Message-Driven Bean (MDB) onMessage() method in a timely way.
Resolution
Perform the following local-change:
Issue will resolve with ActiveMQ resource adapter on JBoss and configuring the Pega MDB to use ActiveMQ in place of HornetQ.
Published May 4, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.