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

MQ listener throws 'Timeout waiting for idle object'



MQ listener in production is throwing 'Caused by: java.util.NoSuchElementException: Timeout waiting for idle object'.

Error Messages

Error reported:

2015-11-11 03:59:54,032 [ MQ-Thread-43] [ STANDARD] [ ] [ AccessGroup:01.01.01] ( ERROR MQ.Test.Test|MQ|PegaSample|Services|ProcessMQ MQ Listener - MQ service [PegaSample][Services][ProcessMQ] failed:Service page lookup Service page lookup failed
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(

... 6 more
Caused by: java.util.NoSuchElementException: Timeout waiting for idle object
at com.pega.apache.commons.pool.impl.GenericObjectPool.borrowObject(
at com.pega.pegarules.session.internal.mgmt.RequestorPool.borrowRequestor(
... 13 more

Steps to Reproduce

We have bounced MQ but continue to exhibit latency with consuming MQ messages in Production environment

Root Cause

A defect in Pegasystems’ code or rules BUG-224476. There seems to be a connectivity issue between database & Pega caused inconsistent state for application requestor pool.


Perform the following local-change: 

Pega server restarted addressed the problem.


Published January 31, 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