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



Not able to retain the lock due to multiple interactions. Obj-Save fails.

Error Messages Error during checkRequiredLocks bean method call: code: <none> SQLState: nested exception is: java.lang.RuntimeException: Problem during method invocation (checkRequiredLocks) Message: <none>

Caused by: nested exception is: java.lang.RuntimeException: Problem during method invocation (checkRequiredLocks)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(

Steps to Reproduce

1. Attach the screenshot of the activity where the Obj-Save fails.
2. Select Write now for Obj-Save.

Root Cause

An issue in the custom application code or rules:
LockGoneException is thrown in one of the custom activities. pyWorkCover page was saved using Obj-Save and Write now was selected. This might create the issue.


Perform the following local-change:

Deselect Write now option, and observe the logs. If the issue still existed, check whether lock is held or not by calling activity WorkLock before Obj-Save. Check other public API under LockManagerInterface.

Published April 12, 2016 - Updated October 8, 2020

Was this useful?

50% 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