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 MDB Listener has multiple instances on single node



Multiple instances of the same JMS MDB Listener were noticed in System Management Application (SMA) on a single node when the listener is processing multiple messages.

Error Messages

Not Applicable

Steps to Reproduce

  1. Configure JMS MDB Listener.
  2. Enter more than five messages into the queue simultaneously.
  3. View the Listeners in SMA.

Root Cause

It is an expected behavior. 


Here's the explanation for the reported behavior:
Everytime a message comes into the queue, onMessage is called in PRPC, and it searches for mListenerID. This method is called asynchronously by JMS when a message arrives at the queue. If it is null, it creates an instance.

Published November 8, 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