topic JobEntity was updated by another transaction concurrently in Alfresco Archive

JobEntity was updated by another transaction concurrently

tomekzaremba — Fri, 19 Feb 2016 10:34:54 GMT

Hi,during stress test of our application most of process instances failed because of exceptionrg.activiti.engine.ActivitiOptimisticLockingException: JobEntity [id=1301291] was updated by another transaction concurrently at org.activiti.engine.impl.db.DbSqlSession$CheckedDeleteOperation.execute(D

Re: JobEntity was updated by another transaction concurrently

tomekzaremba — Fri, 19 Feb 2016 11:02:27 GMT

I see that in jobEntity neither lockOwner nor lockTime are set for job. Why this is not default behavior? Maybe I set this off?

Re: JobEntity was updated by another transaction concurrently

tomekzaremba — Fri, 19 Feb 2016 12:07:44 GMT

I see in user guide:

{code}
The Async executor will execute the asynchronous job directly without first polling the database. In case the asynchronous job is an exclusive job, the Async executor will first lock the process instance execution and if that succeeds execute the job and unlock the process instance execution again. If the process instance lock fails, it will retry.
{code}

My jobs are both asynchronous and exclusive. When I debug and stops on serviceTask my jobEntity still does not have lockOwner and lockTime. Is this correct or is it Activiti bug?

Re: JobEntity was updated by another transaction concurrently

tomekzaremba — Fri, 19 Feb 2016 12:39:36 GMT

My fault - jobs are correctly locked / unlocked. Maybe my retry policy is causing errors in multi-engine environment (R3/PT10S).

Do you have any hints, how can I configure my cluster to handle processing without changing retry policy? Maybe async executor is not suitable solution for me? Maybe ActivitiOptimisticLockException should be handled besides default serviceTask policy - maybe it is proper to change due_date adjusting and don't decrement retries counter?

Re: JobEntity was updated by another transaction concurrently

tomekzaremba — Mon, 22 Feb 2016 05:58:28 GMT

Any hints? How cluster setup should be handled properly with async executor?

Re: JobEntity was updated by another transaction concurrently

jbarrez — Wed, 24 Feb 2016 09:31:32 GMT

Ok, quite a bit of text to read.

The optimistic locking exception os to be expected in a clustered setup, the stalling of course not.
This seems to trigger some vague memory in me. I think we've worked on that (https://github.com/Activiti/Activiti/commit/e59d08629cfe514d7ee23eacd619a6b7bfb509e6) … so it might be good to build a snapshot version and give it a go.

Re: JobEntity was updated by another transaction concurrently

vsk106 — Wed, 09 Nov 2016 18:19:20 GMT

Hi jbarrez,
we are using Alfresco Activiti Enterprise BPM Suite v1.4.5 and we are facing same issue without any cluster for async Service tasks.
Could you please confirm issue has been fixed in v1.4.5 or not ?