Re: jbpm5 Exception:Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#2]
after some inspection of jbpm source code I thinks that jbpm takes usage of optimistic locking. In my case a collision is detected and it is not handled in code :-(. Could someone confirm my thoughts?