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.
Steps to Reproduce
- Set up JMS Listener to subscribe to a topic and start the listener.
- Look at MQ console and see that it is using the system node ID.
- Set up a second member of the cluster.
- Start its listener and see on the MQ Console that a new subscription with the new system's node id has been created.
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.