Support Article
InterruptedException: Requestor has been destroyed or recycled
SA-66051
Summary
Error generated in the logs and system performance degrades.
Error Messages
[-bio-17014-exec-7618] [STANDARD] [<RULESET>:<RULESETVERS>] (ngineinterface.service.HttpAPI) ERROR <IPHOSTNAME>|<IPADDRESS> - <IPADDRESS>: com.pega.pegarules.pub.context.RequestorLockException
com.pega.pegarules.pub.context.RequestorLockException: PRRuntimeException
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1041)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:860)
at com.pega.pegarules.session.internal.engineinterface.service.NonBlockingAPI.postProcessRequestWithLock(NonBlockingAPI.java:282)
…
Caused by: java.lang.InterruptedException: Requestor has been destroyed or recycled
at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.lockAttempt(PRRequestorImpl.java:999)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.getLockOnRequestor(PRSessionProviderImpl.java:1404)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1024)
... 42 more
Steps to Reproduce
Unknown
Root Cause
Data in the log file indicated that the database PARENT and CHILD Save operations failed. This occurred because the MERGE INTO statement (batch processing) did not consider WHICH case was inserted or updated first. That is, the order of CASE persistence to the database (using the MERGE INTO statement) was non-deterministic.
Resolution
Perform the following local-change:
Disable the MERGE INTO statement using the following updates to the Process Commander prconfig.xml settings:
<env name="classmap/usemergestatement" value ="false" />
<env name="database/batchupdates" value="-1" />
Tags:
Published October 10, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.