"Save, Delete or Commit has failed because lock is not held" error when resolve case
Hi
We got below error message from our production enviroment.
ERROR - obj-save failed.
com.pega.pegarules.pub.database.LockGoneException: Save, Delete or Commit has failed because lock "XXXXXX" is not held.
And at that moment, user was doing case resolve but could not resolve case successfully. I have found below SA article which has the same situation with us:
https://pdn.pega.com/support-articles/save-delete-or-commit-has-failed-because-lock-not-held-0
GoalTime: Oct 4, 2017 12:00:00 PM
ERROR: Oct 5, 2017 6:29:09 PM
DeadlineTime: Oct 5 2017 12:00:00PM
In my understanding, this error occurred when using Obj-Open without selecting "Lock" checkbox in customized activity. But I don't know why setting GoalTime to zero will cause this issue, could anyone explain the root cause please?
*We are using PRRC ver 7.2 and in order to resolve case, Call OOTB activity "UpdateStatus" by passing "Resolved-XXXX" to StatusWork parameter and then Call "commitWithErrorHanding".
Thanks
Pegasystems Inc.
US
Hi Shubhi,
I had reviewed the information regarding the root cause of the issue in the above Support Article, but couldn't find much information. As per my understanding, as the goal time of sla is 0, then Agent will process this item and the work item will become stale which in turn will cause the above error when we try to resolve it. May be others can share if they find any further information regarding this issue.
Hope this might help you.
Regards
Mahesh
Pegasystems Inc.
IN
To process any case we need to set a goal time which is measured from the time that a case is created to the time that the case is resolved. SO to process the case we need to have a goal time if this is set to 0we would get this error.
Hope this helps.
Thanks,
Ashwani