Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Review PRAsyncTopic configuration for cluster and suggest



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.


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

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us