topic Re: org.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[423472] was updated by another transaction concurrently in Alfresco Archive

org.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[423472] was updated by another transaction concurrently

jdp — Thu, 03 Mar 2016 11:52:07 GMT

Hi,I have a workflow designed as attached, when this workflow run in below mentioned steps, it is throwing 'org.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[423472] was updated by another transaction concurrently' error.Step: 1. Tasks U1, S1, S2 are completed.2. When system i

Re: org.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[423472] was updated by another transaction concurrently

jdp — Thu, 03 Mar 2016 11:53:21 GMT

Sorry not able to attach workflow image here.. as only .txt files are allowed.

Re: org.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[423472] was updated by another transaction concurrently

jbarrez — Mon, 07 Mar 2016 09:24:03 GMT

That exception typically means that multiple threads are doing something to the process instance.
Do you have multiple engines running with job executor enabled?

Attach the process xml as txt to this post so we can see if there's something else up.

Re: org.activiti.engine.ActivitiOptimisticLockingException: ProcessInstance[423472] was updated by another transaction concurrently

jdp — Mon, 28 Mar 2016 11:12:13 GMT

Hi jbarrez,

Thanks for the reply. Sorry I am replying too late but was stuck with something else.

As you mentioned, Yes there are multiple threads accessing same process instance. Actually completion calls for four different parallel nodes reaches at same time and one system task is already running, in this case this problem occurred.

I had solved this problem by making same instance calls in Synch, So now all calls of same process instance will execute sequentially.
Yes, I am using multiple Activiti engines, 2 for now. So I had applied Synch mechanism across all Activiti engines using distributed locking mechanism.

Now I am facing below mentioned problem frequently, please refer this case as well, however this case is related to multiple threads are accessing different process instance same time :
https://forums.activiti.org/content/deadlocked-while-deleting-records-actruexecution-multiple-activiti-engines-running

Please provide your thoughts/suggestions for the same. Is this a right solutions for the situation ?

Thanks,
JDP