Support Article
Lock gone exceptions in log
SA-21849
Summary
Not able to retain the lock due to multiple interactions. Obj-Save fails.
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) Message: <none>
Caused by:
com.ibm.ejs.container.UnknownLocalException: nested exception is: java.lang.RuntimeException: Problem during method invocation (checkRequiredLocks)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:444)
.
.
.
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.
Resolution
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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.