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

Lock lost error in Tomcat instance but not in JBoss



You have a Tomcat/JBoss concurrent environment. You get a LockLost exception when you create a new work object. The LockLost exception occurs in Tomcat but not in JBoss.

Error Messages

** Database-LockFailure-LockLost ClassName WorkObject-ID
** Save, Delete or Commit has failed because lock "ClassName WorkObject-ID" is not held

Steps to Reproduce

  1. Run a flow that creates a new work object.
  2. Observe the error message.

Root Cause

The root cause of this problem is a defect/misconfiguration in the PRPC 6.3 SP1 operating environment.


You can resolve the issue by making one of the following changes:
  1. Bring up the Tomcat nodes before bringing up the JBoss nodes.
  2. Do not have a Tomcat/JBoss concurrent environment.

Published January 31, 2016 - Updated October 8, 2020

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