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

Intermittent LockGoneException in the log file

SA-38745

Summary



User is using PRPC 6.3 SP1 with Pega CS for Financial Services 6.3.1.

User reports intermittently that the assignment is processing error while working on the case. When they analyzed the log they found out that there are lot of "LockGoneException" error message in the log frequently.


Error Messages



Error message in the Pega log file.

obj-save failed.
com.pega.pegarules.pub.database.LockGoneException: Save, Delete or Commit has failed because lock "XXXXXXX" is not held


Steps to Reproduce



There is no specific reproducible scenario.


Root Cause



This was determined to be a environment issue, since the Weblogic connection pool settings seems to be too low.

Resolution



User is suggested to fine tune the JDBC Connection pool settings.
Suggest Edit

Published July 10, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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