Support Article
MQ listener throws 'Timeout waiting for idle object'
SA-17511
Summary
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] ( internal.services.ServiceAPI) ERROR MQ.Test.Test|MQ|PegaSample|Services|ProcessMQ MQ Listener - MQ service [PegaSample][Services][ProcessMQ] failed:Service page lookup failed:com.pega.pegarules.pub.services.ServiceException: Service page lookup failed
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.preLockSetup(ServiceAPI.java:1040)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:323)
... 6 more
Caused by: java.util.NoSuchElementException: Timeout waiting for idle object
at com.pega.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:751)
at com.pega.pegarules.session.internal.mgmt.RequestorPool.borrowRequestor(RequestorPool.java:463)
... 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.
Resolution
Perform the following local-change:
Pega server restarted addressed the problem.
Published January 31, 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.