[jboss-user] [jBPM] - Re: jbpm5 Exception:Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#2]

Mauricio Salatino [http://community.jboss.org/people/salaboy21] created the discussion "Re: jbpm5 Exception:Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.persistence.processinstance.ProcessInstanceInfo#2]" To view the discussion, visit: http://community.jboss.org/message/632503#632503 -------------------------------------------------------------- Hi guys, yes I can confirm Daniel's point.. jBPM5 by default use optimistic locking and if two or more threads load the same representations and modify them one of them will fail and the other will succeed. You can change the locking strategy if you want to avoid that, or you can implement a retrying mechanism for the failing thread. Cheers -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/632503#632503] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]