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

Missing message in PEGA SI because of JMS listener issues



You fail to receive some incoming messages due to a JMS Service Listener issue.

Error Messages

a) 2015-05-15 11:22:57,767 [20550502962094B701]]] [ STANDARD] [ ] ( internal.mgmt.PREnvironment) ERROR - Problem obtaining requestor from ServiceRequestorPool Timed out borrowing service requestor from requestor pool
From: (unknown)
at com.pega.pegarules.session.internal.mgmt.RequestorPool.borrowRequestor(

b) 2015-05-15 11:22:57,779 [20550502962094B701]]] [ STANDARD] [ ] (tener.ListenerStateManagerImpl) ERROR - Failed to create MDB Listener Unable to create listener instance - PegaTestJMSLISTENER

Steps to Reproduce

Not Applicable

Root Cause

The root cause of this problem is defect/misconfiguration in the operating environment. Service Activity calls result in DB queries that take long time to complete and the Service Package is defined as Authenticated Stateless so burst of JMS messages quickly consume all the App requestors available in the pool resulting in failure to borrowRequestor.


This issue is resolved through the following local change: Change the Service Package for Service JMS to use Stateless Unauthenticated configuration and increase the Max, Min and Idle requestor pooling config to the desired value on par with expected load and Service Activity performance.

Published February 27, 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