Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

LockGoneExceptions occur in logs while performing Obj-Save




LockGoneExceptions occur in logs while performing the Obj-Save.

Error Messages


[PegaRULES-Batch-5] [STANDARD] [ ] [EWS:] (ExecuteSLA.Assign_.Action) ERROR - obj-save failed. Save, Delete or Commit has failed because lock "Classname-ABC-XX" is not held
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_executesla_43e15f8b7af276e6fe98916df460ae87.step23_circum0( ~[?:?]
at com.pegarules.generated.activity.ra_action_executesla_43e15f8b7af276e6fe98916df460ae87.perform( ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity( ~[prprivate.jar:?]
at com.pegarules.generated.activity.ra_action_ewsservicelevelevents_8a6249df1e9f523acb159570539f1f89.step7_circum0( ~[?:?]
at com.pegarules.generated.activity.ra_action_ewsservicelevelevents_8a6249df1e9f523acb159570539f1f89.perform( ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute( ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked( ~[prprivate.jar:?]
at ~[prprivate.jar:?]
at ~[prjsr166java6-3.0.jar:?]
at$ ~[prjsr166java6-3.0.jar:?]
at [?:?]


Steps to Reproduce

  1. Configure an agent  which runs every 30 seconds
  2. Configure Obj-Save in the agent activity. Exceptions occur in logs


Root Cause

An issue in the custom application code or rules. 


Perform the following local-change:
Set the Dynamic System Setting (DSS) Database/transactionallockmanagement to standard.



Published February 22, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us