topic Re: getting Exception org.activiti.engine.ActivitiOptimisticLockingException in Alfresco Archive

getting Exception org.activiti.engine.ActivitiOptimisticLockingException

sharad — Fri, 28 Feb 2014 05:51:34 GMT

I am using Activiti 5.14. I have created one bpmn that contains multi instance subprocess and we have created Service task within subprocess. Only one process engine is running in our environment. We are getting org.activiti.engine.ActivitiOptimisticLockingException while enabled async property of s

Re: getting Exception org.activiti.engine.ActivitiOptimisticLockingException

trademak — Sat, 01 Mar 2014 13:52:01 GMT

The problem is that with an async multi instance sub process + an async service task within that sub process, a service task can end concurrently within the multi instance scope. Is there a specific reason to make the service task async? Are they long running?

Best regards,

Re: getting Exception org.activiti.engine.ActivitiOptimisticLockingException

sharad — Wed, 12 Mar 2014 07:19:56 GMT

Yes, Service task are taking long time. We want to run service task in asynce manner. When I set Multi instance -> Sequential attribute to true of Multi Instance Sub process then there was no Exceptions. In that case, service task are running on multiple thread but in a sequential manner even if I have set Asynchronous option for sub process and service task to true. We want to run those service task in async manner.

How do we achieve async Multi instance sub process with async service task without any exception ?

Do we need to handle ActivitiOptimisticLockingException in our project ?

Re: getting Exception org.activiti.engine.ActivitiOptimisticLockingException

jorell — Mon, 04 Aug 2014 21:45:41 GMT

I am having the same issue. Was there any solution to this?

Re: getting Exception org.activiti.engine.ActivitiOptimisticLockingException

frederikherema1 — Wed, 06 Aug 2014 08:46:49 GMT

If you run multi-instance service tasks asynchronously, you can indeed run into Optimistic lock exceptions, when 2 async executions end about the same time. If you need to do long-running parallel execution, maybe you can take a look at integrating Camel, for example.

Having long-running stuff happening in a ServiceTask will keep the transaction open. It can result in transaction timeouts or (in case transaction timeout > 5 minutes) have the job be considered "hanging", having the job unlocked and retried by the job-executor…

Re: getting Exception org.activiti.engine.ActivitiOptimisticLockingException

box — Sat, 28 Mar 2015 13:02:06 GMT

I am having the same issue. firstly I find the Job lock time is 5min but our service tasks remain unfinished, so set the JobExecutor lock time to larger(60min)，concurrent is disappeared,is this work ? thanks

Re: getting Exception org.activiti.engine.ActivitiOptimisticLockingException

trademak — Sun, 29 Mar 2015 17:56:09 GMT

Which version of Activiti are you using? Since version 5.17 we improved the job executor with a new async executor. Did you take a look at that?

Best regards,

Re: getting Exception org.activiti.engine.ActivitiOptimisticLockingException

box — Mon, 30 Mar 2015 02:22:43 GMT

yes ，I know in version 5.17 job executor with a new async executor which is good, but currently we using Activiti 5.14，we guarantee the execution variables only readable after set. In multi subprocess ，when multi thead runing a async service task ActivitiOptimisticLockingException happen. so we set the lock time to 60min，It seem work, but I not sure is ActivitiOptimisticLockingException may happen where in other special scene?