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

Lock gone exceptions in log related to CPM



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 Error during checkRequiredLocks bean method call: code: <none> SQLState: nested exception is: java.lang.RuntimeException: Problem during method invocation (checkRequiredLocks)
Caused by: 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.


HFIX-10093 resolved the issue.

Published January 31, 2016 - Updated December 2, 2021

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