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

JMS listener does not support durable subscriber in a cluster



User has a problem with setting up JMS listener(not MDB(Message-Driven Bean)) in a cluster(multiple nodes point to same rulebase) & want these listeners to subscribers to a topic. User is using Redhat Active Message Queue as messaging server. The problem with this is that if multiple listeners on the same cluster subscribe to the same topic, each gets a message to be processed instead of just one message.

Error Messages

Not applicable.

Steps to Reproduce

  1. Set up JMS Listener to subscribe to a topic and start the listener.
  2. Look at MQ console and see that it is using the system node ID.
  3. Set up a second member of the cluster.
  4. Start its listener and see on the MQ Console that a new subscription with the new system's node id has been created.

Root Cause

A defect in Pegasystems’ code or rules. 


Perform the following local-change: 

Implement a solution using 'Virtual destination' feature of the Redhat Active MQ.
In this implementation, each subscriber is assigned a queue and message provider pushes messages to subscriber queue. JMS listener listens to one of those queues, hence receives only one copy of the message.


Suggest Edit

Published October 1, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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