Transaction issues when a jBPM work item uses a new RuntimeManager after a Human Task call in BPM Suite 6

Solution Verified - Updated -


  • In a custom work item after a Human Task, if it is needed to get the KieSession from a new RuntimeManager the exception below is thrown:
javax.persistence.OptimisticLockException: org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#1]


  • Red Hat JBoss BPM Suite (BPMS)
    • 6.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In