Support Article
Commit and Save fails with LockGoneException for Interactions
SA-19021
Summary
User has reported ''LockGoneException' in logs for interactions and ‘Commit' and 'Save' is failing for about 4-5 Interactions per day.
Error Messages
2016-01-02 09:03:13,417 [.140.86-80-exec-3969] [WorkThread] [ ] ] (Parent.PegaCA_Work.Action) ERROR - obj-save failed.
com.pega.pegarules.pub.database.LockGoneException: Save, Delete or Commit has failed because lock "<YOUR_COMPANY>-WORK-INTERACTION I-12345" is not held
From: (HD94DED4ED4C1B26C54E2017099988F96:)
at com.pega.pegarules.data.internal.access.LockManagerImpl.checkRequiredLocks(LockManagerImpl.java:1166)
at com.pega.pegarules.data.internal.access.DatabaseImpl.checkRequiredLocks(DatabaseImpl.java:2265)
at com.pega.pegarules.data.internal.access.DatabaseImpl.attemptToProcessUpdates(DatabaseImpl.java:2646)
at com.pega.pegarules.data.internal.access.DatabaseImpl.processUpdates(DatabaseImpl.java:2308)
at com.pega.pegarules.data.internal.access.Saver.save(Saver.java:651)
at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:5045)
at com.pega.pegarules.data.internal.access.DatabaseImpl.save(DatabaseImpl.java:5031)
at com.pegarules.generated.activity.ra_action_caresumeparent_1c742530594df0be7484cec58beb2084.step7_circum0(ra_action_caresumeparent_1c742530594df0be7484cec58beb2084.java:906)
at com.pegarules.generated.activity.ra_action_caresumeparent_1c742530594df0be7484cec58beb2084.perform(ra_action_caresumeparent_1c742530594df0be7484cec58beb2084.java:185)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10521)
at com.pegarules.generated.activity.ra_action_careturntocaller_598f91bb53fe3a327dc3a39dc7014879.step9_circum0(ra_action_careturntocaller_598f91bb53fe3a327dc3a39dc7014879.java:968)
at com.pegarules.generated.activity.ra_action_careturntocaller_598f91bb53fe3a327dc3a39dc7014879.perform(ra_action_careturntocaller_598f91bb53fe3a327dc3a39dc7014879.java:228)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3500)
Steps to Reproduce
Encountere LockGoneException trace when performing a Commit. Observe that Obj-Save fails.
Root Cause
In certain scenarios for caresumeparent activity, Obj-Save of parent page was happening, when lock is lost resulting into the error.
Resolution
Perform the following local-change:
Add Obj-Refresh-and-Lock step before Obj-Save for parent page and that ensures that the lock is always held before commit.
Published January 31, 2016 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.