Support Article
Review PRAsyncTopic configuration for cluster and suggest
SA-21259
Summary
Review PRAsyncTopic configuration for cluster and suggest
Error Messages
Not Applicable
Steps to Reproduce
Not Applicable
Root Cause
Pega out of the box setup uses PRAsyncTopic destination for internal engine processing and messages sent to this destination meant for the local JVM.
Resolution
Here’s the explanation for the reported behavior:
User reconfigured PRAsyncTopic destination from the cluster level to local JVM level. With JMS resources targeted at cluster level, JMS messages are duplicated in multiple nodes.
Published March 23, 2016 - 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.