Question
Matlen Silver
US
Last activity: 26 Apr 2016 22:30 EDT
SLA broken items queue: Save, Delete or Commit has failed because lock
Dear All,
I am getting the following error due to different handles(flows invoking assignments with SLAs). I see this error when go to: Process & Rules > Tools > My Work Admin > Broken Queue Items > System-Queue-ServiceLevel
Error Message:
<pxErrorMessage>Save, Delete or Commit has failed because lock "{lock or work object here}" is not held</pxErrorMessage>
I am guessing this a PEGA code related issue but please let me know if you have faced this situation before or if you have a fix for that.
I have gone through some related forums(https://pdn.pega.com/support-articles/advance-flow-does-not-work-subcase) already but seems my situation is different since the Access Group who initiated the the wait shape is the same with the current operator logged in.
Thanks a lot,
Byron
Pegasystems Inc.
US
Check these PDN links :
Pega 6.3sp3 https://pdn.pega.com/support-articles/save-delete-or-commit-fails-because-lock-not-held
How is the class defined? Does it have "Allow locking" selected?
Pegasystems
US
During normal flow processing, the work object is saved (for instance, in the RecalculateAndSave activity) and then committed (n the CommitWithErrorHandling activity), although if you have an error stack, you may be able to see more accurately where the save is being attempted.
A lock is required in order for that save to be allowed, and if you do not hold the lock, you get the error you showed above.
Some things to check:
1) If you're using flow processing, the system acquires the lock for you, but if you have to acquire it, such as with the "lock" checkmark on an obj-open, make sure you use something like the "StepStatusFail" test to make sure you actually got the lock.
2) As mentioned, flow processing normally does the obj-open for you, but if you happened to do it, see whether you used the "release on commit" checkmark, since if you did, and the lock got released during the commit, that could explain why you're getting the error.
3) Once you have the lock, if you're using flow processing, the system handles all the saves and commits for you, so you shouldn't have to do any obj-save. But if you do, see whether you kept the lock or released it.
/Eric