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

Agents not processing & Long running requestor with thread dump



Users reported that long running requestors sessions with thread dumps getting generated in the PegaRULES log file.

Error Messages

[9/9/14 10:18:29:137 EDT] 0000001f SystemOut     O 2014-09-09 10:18:29,134 [prpc_ws61,maxpri=10]] [  STANDARD] [                    ] (          engine.context.Agent) WARN    - Long running request detected for requestor BB9DFFFDEC9599BF6A8687EE5C917F74E on java thread java.lang.ThreadGroup[name=opc_wm: opc_prpc_ws61,maxpri=10] for approximately 1834 seconds -- requesting thread dump.

Thread[java.lang.ThreadGroup[name=opc_wm: opc_prpc_ws61,maxpri=10],5,opc_wm: opc_prpc_ws61] Method)
    at Source)
    at oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(
    at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(
    at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(
    at oracle.jdbc.driver.T4CTTIfun.receive(
    at oracle.jdbc.driver.T4CTTIfun.doRPC(
    at oracle.jdbc.driver.T4C8Oall.doOALL(
    at oracle.jdbc.driver.T4CCallableStatement.doOall8(
    at oracle.jdbc.driver.T4CCallableStatement.executeForRows(
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
    at oracle.jdbc.driver.OraclePreparedStatement.execute(
    at oracle.jdbc.driver.OracleCallableStatement.execute(
    at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(
    at com.pega.pegarules.engine.database.DatabasePreparedStatement.execute(
    at com.pega.pegarules.engine.database.DatabaseImpl.list(
    at com.pega.pegarules.engine.database.DatabaseImpl.executeRDB(
    at com.pega.pegarules.engine.database.DatabaseImpl.executeRDB(
    at com.pega.pegarules.engine.context.agent.QueueManagerImpl$
    at com.pega.pegarules.engine.context.agent.QueueManagerImpl$

Root Cause

Users had lack of memory on the shared oracle database. Requested user to review the diagnostic data available along with Pega0019 alerts.

PDN Link -


Issue was due to lack of memory on the database causing long running requestor sessions. 

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