Why are we seeing race conditions in the jBPM LockMonitorThread after migrating to SOA-P 4.3.0 CP02?

Solution Verified - Updated -

Issue

After we have migrated to SOA-P 4.3.0 CP02, we see the following exception every now and then:

ERROR [org.hibernate.event.def.AbstractFlushingEventListener] (JbpmJobExector:LockMonitorThread@169.1.1.1) 
Could not synchronize database state with session
org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction 
(or unsaved-value mapping was incorrect): [org.jbpm.job.ExecuteActionJob#123]

Environment

  • JBoss Enterprise SOA Platform (SOA-P) 4.3.0 CP02

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content