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.
** Database-LockFailure-LockLost ClassName WorkObject-ID
** Save, Delete or Commit has failed because lock "ClassName WorkObject-ID" is not held
Steps to Reproduce
- Run a flow that creates a new work object.
- Observe the error message.
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:
- Bring up the Tomcat nodes before bringing up the JBoss nodes.
- 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.