Support Article
PegaRules agents run indefinitely at runtime on JBoss
SA-58519
Summary
Two nodes are running on JBoss EAP 6.4. The RuleUsageSnapshot out-of-the-box agent is set to run once a day (recurring pattern) and is scheduled at different times on each node.
On one of the nodes, after waking up on schedule, the RuleUsageSnapshot runs indefinitely. As a result, other agents (Pega-RULES, Pega-RulesEngine) stop running. In the System Management Application (SMA), the next run time displays in the past.
Error Messages
Not Applicable
Steps to Reproduce
Not Applicable
Root Cause
A defect or configuration issue in the operating environment.
Resolution
Apply HFix-27523 (for the SystemCleaner agent).
For the RuleUsageSnapshot agent, a bug in JBoss exists. As a result, when an agent takes a long time to run, the agent runs indefinitely and all the other agents stop running.
As a local-change, modify the following:
Set consumer-window-size to 0
Set max-delivery-attempts to 1
Set redelivery-delay to 0
The configurations in JBOSS are as below:
<pooled-connection-factory name="hornetq-ra"> <transaction mode="xa"/> <connectors> <connector-ref connector-name="in-vm"/> </connectors> <entries> <entry name="java:/JmsXA"/> </entries> <consumer-window-size>10240</consumer-window-size> <!-- HERE --> .... .... .... </pooled-connection-factory>
<address-setting match="#"> <dead-letter-address>jms.queue.DLQ</dead-letter-address> <expiry-address>jms.queue.ExpiryQueue</expiry-address> <redelivery-delay>0</redelivery-delay> <!-- HERE --> <max-size-bytes>10485760</max-size-bytes> <address-full-policy>PAGE</address-full-policy> <page-size-bytes>2097152</page-size-bytes> <max-delivery-attempts>1</max-delivery-attempts> <!-- HERE --> <message-counter-history-day-limit>10</message-counter-history-day-limit> </address-setting>
Published December 29, 2018 - 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.