topic Re: using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0 in Alfresco Archive

using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0

gavin_huang — Sat, 22 Oct 2016 10:06:28 GMT

Hi, In my workflow, 1. there is a Multi-instance sub-process 2. the task on Subprocess are service task 3. all "service task" set activiti:async="true" activiti:exclusive="false"the image as attachementthe config as follow:<bean id="asyncExecutor" class="org.activiti.engine.impl.asyncexecu

Re: using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0

gavin_huang — Sat, 22 Oct 2016 10:11:55 GMT

Re: using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0

cjose — Fri, 28 Oct 2016 05:18:43 GMT

Looks like you are spinning off multiple parallel sub-processes and from those sub-processes you are trying to update a common variable nrOfActiveInstances. Hence this optimistic locking exception to prevent concurrent updates on a variable.

Re: using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0

gavin_huang — Tue, 01 Nov 2016 14:13:47 GMT

Yes, I am spinning off multiple parallel sub-processes and know this optimistic locking exception to prevent concurrent updates on a variable. But how to solve this exception when using multiple parallel sub-processes?
My code do not try to update this common variable nrOfActiveInstances, is the multiple parallel sub-processes. So I do not know how to use multiple parallel sub-processes without optimistic locking exception.

Re: using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0

warper — Wed, 02 Nov 2016 10:32:00 GMT

Hi Gavin!

>all "service task" set activiti:async="true" activiti:exclusive="false"
You can start instances in different executions if you set async=true, exclusive=false and sequential=false in multi-instance settings. Why do you want to add more async points in subprocesses?

Re: using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0

cjose — Sun, 06 Nov 2016 06:13:34 GMT

Since your subprocesses contains just a two service tasks, the chances of these subprocesses ending at the same time is more and hence the variable update happening at the same time. Since I'm not across your complete use-case, it's very difficult to give a solution with the current available information. Since all your tasks inside the subprocess are set to async, setting maxAsyncJobsDuePerAcquisition=1 in your config might help complete the subprocess, one at a time.

Ciju.

Re: using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0

thuynh — Mon, 19 Dec 2016 17:10:16 GMT

Hi Gavin,

Your process definition xml seems fine. For your information, here are the Activiti user guides on Multi-Instance (http://www.activiti.org/userguide/#bpmnMultiInstance) and Async Executor (http://www.activiti.org/userguide/#jobExecutorConfiguration).

So I believe the following settings should be enough to get you going with Activiti Multi-Instance and Async. It worked for me.

Enable Multi-Instance for the subprocess by defining multi-instance sequential to false and the carnality.
Enable SyncExecutor in activiti-cfg.xml (see my attached cfg,xml)
For the service tasks to be executed asynchronously, check 'Asynchronous' (see my attached process definition xml)
Leave the 'Exclusive' checkbox default (checked) (see my attached process definition xml and documentation why you should leave it default, http://www.activiti.org/userguide/#exclusiveJobs).

Testing this in a unit test can be troublesome as you are testing async jobs which can complete or not complete by the time the Junit test completes.

Here is a snippet of my unit test log showing that the service tasks were executed asynchronously in the multi-instance loop.

-------------------------------------------------------

T E S T S

-------------------------------------------------------

Running org.activiti.designer.test.MultiInstanceTest

Dec 19, 2016 12:18:34 PM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions

INFO: Loading XML bean definitions from class path resource [activiti.cfg.xml]

Dec 19, 2016 12:18:36 PM org.activiti.engine.impl.db.DbSqlSession executeSchemaResource

INFO: performing create on engine with resource org/activiti/db/create/activiti.h2.create.engine.sql

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.db.DbSqlSession executeSchemaResource

INFO: performing create on history with resource org/activiti/db/create/activiti.h2.create.history.sql

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.db.DbSqlSession executeSchemaResource

INFO: performing create on identity with resource org/activiti/db/create/activiti.h2.create.identity.sql

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.ProcessEngineImpl <init>

INFO: ProcessEngine default created

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor start

INFO: Starting up the default async job executor [org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor].

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor startExecutingAsyncJobs

INFO: Creating thread pool queue of size 100

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.asyncexecutor.DefaultAsyncJobExecutor startExecutingAsyncJobs

INFO: Creating executor service with corePoolSize 2, maxPoolSize 10 and keepAliveTime 5000

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.asyncexecutor.AcquireTimerJobsRunnable run

INFO: {} starting to acquire async jobs due

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.asyncexecutor.AcquireAsyncJobsDueRunnable run

INFO: {} starting to acquire async jobs due

Dec 19, 2016 12:18:37 PM org.activiti.engine.impl.bpmn.deployer.BpmnDeployer deploy

INFO: Processing resource multiInstanceProcess.bpmn20.xml