Close popover
Lei Zhong (LeiZ4221)
NJ Courts

NJ Courts
LeiZ4221 Member since 2016 10 posts
NJ Courts
Posted: June 9, 2017
Last activity: August 23, 2017

Is it best practice to run JMS MDB Listener on all server Nodes?

Our production is getting information from other system through JMS message. We configured MQ in WAS and created JMS MDB Listener in Pega. It's working very well. But we came to know that around 5% messages are duplicated, as per we checked with JMS sender, they didn't send duplicated messages.

We have 4 server Nodes. PegaRULES logs captured the duplicated service Activity calls. The duplication happens almost in the same second. I'm suspecting 2 listeners woke up at the same time and picked up the same message from MQ, but I can't verify that. Please see attached time stamps in the logs.

Is it best practice to run JMS MDB Listener on all server Nodes? I thought if any Listener picked it up, the queued message should went away.

If my thought was wrong, how should I trace the listener? so that I know where the duplicated message from.

***Updated by moderator: Lochan to add SR details***

Data Integration Support Case Created
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.