topic Re: Activiti Optimistic Lock Exception with multiple process engines. in Alfresco Forum

Activiti Optimistic Lock Exception with multiple process engines.

gjaya26 — Fri, 23 Feb 2018 21:01:08 GMT

We have a bpmn definition, using which we generate about 70K workflows each quarter. All this time, we were creating workflows only in one database. There is an organizational pitch to create workflows in multiple databases. After we introuduced multiple database configuration, we noticed optimistic

Re: Activiti Optimistic Lock Exception with multiple process engines.

ryandawson — Mon, 26 Feb 2018 09:43:51 GMT

Yes I would expect there not to be any data loss. An issue like this was discussed recently and in that case also there was no data loss JobEntity [id=*****] was updated by another transaction concurrently The error suggests that two engines are trying to do the same thing at the same time and only one of them therefore succeeds (i.e. a race condition). As covered in the referenced thread, this is more likely to happen with async tasks and more likely with v5 than v6. Are you seeing the error on an async task/s? If you could share your process definition and which part you see the error on that would help. From the error it looks like you have a form on a task - is the error always related to that form? Are you using v5?

Re: Activiti Optimistic Lock Exception with multiple process engines.

gjaya26 — Mon, 26 Feb 2018 14:39:43 GMT

Yes, we are using version 5. The bpmn file is attached at the location:

The error occurs when we try to create workflows. there are about 70K workflows. The error also occurs when the system tries to move a workflow automatically from preparer na to controller na state.

Re: Activiti Optimistic Lock Exception with multiple process engines.

ryandawson — Mon, 26 Feb 2018 15:41:03 GMT

I suspect the parallelGateway is the reason the jobExecutor is in use even though you don't have anything explicitly marked async. You could try turning off jobExecutorActivate and asyncExecutor (using settings in clustering with async tasks and the async executor ) see if it all still works. Other paths available to try are switching to the async job executor and/or upgrading to v6. Other threads on this are using asyncExecutor but ActivitiOptimisticLockingException on activiti 5.21.0 and Enable jobExecutorActivate - Impact .

Re: Activiti Optimistic Lock Exception with multiple process engines.

Anonymous — Mon, 26 Feb 2018 16:08:14 GMT

It might not be an infrastructure, it's just a process problem.

In your process definition, you are connecting from the parallel gateway to the exclusive gateway.

After the exclusive gateway, then two more executions will move.

Re: Activiti Optimistic Lock Exception with multiple process engines.

gjaya26 — Tue, 27 Feb 2018 19:33:53 GMT

Hi daisuke,

This is how the requirements are laid out. At the start, they want to have both the tasks in parallel. User can take action only on one task. After the user takes action, eg: let us say preparer approval, the preparer na task should no longer be available and the next set of tasks need to be created.

I am not sure if i can remove the gateways above and still satisfy the requirement.

Re: Activiti Optimistic Lock Exception with multiple process engines.

gjaya26 — Tue, 27 Feb 2018 20:07:35 GMT

Hi Ryan,

If we turn off jobExecutorActivate, then when the user takes action, would the workflow state move forward?

Re: Activiti Optimistic Lock Exception with multiple process engines.

Anonymous — Wed, 28 Feb 2018 16:56:56 GMT

No. You don't need to remove gateway. You need to replace Exclusive Gateway to Parallel Gateway.

In your process definition, you are connecting from the parallel gateway to the exclusive gateway.

After the exclusive gateway, two executions will be generated and do not match the requirements.