Support Article
Agents not processing & Long running requestor with thread dump
SA-1445
Summary
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]
java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at oracle.net.ns.Packet.receive(Packet.java:282)
at oracle.net.ns.DataPacket.receive(DataPacket.java:103)
at oracle.net.ano.CryptoDataPacket.receive(Unknown Source)
at oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:230)
at oracle.net.ns.NetInputStream.read(NetInputStream.java:175)
at oracle.net.ns.NetInputStream.read(NetInputStream.java:100)
at oracle.net.ns.NetInputStream.read(NetInputStream.java:85)
at oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:122)
at oracle.jdbc.driver.T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:78)
at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1179)
at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1155)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:279)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:202)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1005)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3550)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4710)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecute(WSJdbcPreparedStatement.java:938)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute(WSJdbcPreparedStatement.java:614)
at com.pega.pegarules.engine.database.DatabasePreparedStatement.execute(DatabasePreparedStatement.java:833)
at com.pega.pegarules.engine.database.DatabaseImpl.list(DatabaseImpl.java:4409)
at com.pega.pegarules.engine.database.DatabaseImpl.executeRDB(DatabaseImpl.java:4657)
at com.pega.pegarules.engine.database.DatabaseImpl.executeRDB(DatabaseImpl.java:4625)
at com.pega.pegarules.engine.context.agent.QueueManagerImpl$QueueIteratorImpl.next(QueueManagerImpl.java:1703)
at com.pega.pegarules.engine.context.agent.QueueManagerImpl$QueueIteratorImpl.next(QueueManagerImpl.java:1630)
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 - https://pdn.pega.com/performance/understanding-the-pega0019-alert-long-running-requestor-detected
Resolution
Issue was due to lack of memory on the database causing long running requestor sessions.
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.