Support Article
Missing message in PEGA SI because of JMS listener issues
SA-10588
Summary
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
com.pega.pegarules.pub.PRException: Timed out borrowing service requestor from requestor pool
From: (unknown)
at com.pega.pegarules.session.internal.mgmt.RequestorPool.borrowRequestor(RequestorPool.java:464)
b) 2015-05-15 11:22:57,779 [20550502962094B701]]] [ STANDARD] [ ] (tener.ListenerStateManagerImpl) ERROR - Failed to create MDB Listener
com.pega.pegarules.pub.PRException: 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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.