Lock gone exceptions in log
Not able to retain the lock due to multiple interactions. Obj-Save fails.
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>
com.ibm.ejs.container.UnknownLocalException: nested exception is: java.lang.RuntimeException: Problem during method invocation (checkRequiredLocks)
Steps to Reproduce
1. Attach the screenshot of the activity where the Obj-Save fails.
2. Select Write now for Obj-Save.
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.
50% found this useful