Question

2
Replies
3015
Views
Close popover
Shubi Yang (ShubiY62)
Accenture
Senior System Architect
Accenture
JP
ShubiY62 Member since 2016 20 posts
Accenture
Posted: October 6, 2017
Last activity: October 6, 2017
Closed

"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

Data Integration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.