Support Article
Lock gone exceptions in log related to CPM
SA-1888
Summary
There are a large number of LockGoneExceptions in the PegaRULES logfile. These seem to occur after the the wrap up of the interaction has completed and the wrap up tab has been closed.
Error Messages
com.pega.pegarules.pub.database.DatabaseException: Error during checkRequiredLocks bean method call: code: <none> SQLState: nested exception is: java.lang.RuntimeException: Problem during method invocation (checkRequiredLocks)
...
Caused by:
com.ibm.ejs.container.UnknownLocalException: nested exception is: java.lang.RuntimeException: Problem during method invocation (checkRequiredLocks)
Steps to Reproduce
1. Start a new interaction
2. Search for and select an account
3. When the composite is displayed, choose wrap up
4. Wrap up the interaction
5. Check the logs to see errors.
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules. The activity CAQueuedTasksVertical_ToDo is called multiple times on any interaction and will release lock, resulting in Lock Gone exceptions on the second and subsequent calls.
Resolution
HFIX-10093 resolved the issue.
Published January 31, 2016 - 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.