topic Re: JobEntity exception in Alfresco Archive

JobEntity exception

r3dge — Wed, 25 May 2016 09:41:15 GMT

Hi all,I get an exception message in table act_ru_job : "JobEntity [id=44142329] was updated by another transaction concurrently".Process instances are stopped in a service task without triggering the boundary error (as it does normally).I have no idea to fix this problem. Could you help to analyse

Re: JobEntity exception

r3dge — Wed, 25 May 2016 09:50:40 GMT

some precisions : i'm using Activiti 5.17.

Thanks for your help

Re: JobEntity exception

martin_grofcik — Wed, 25 May 2016 11:28:58 GMT

Hi,

Can you create jUnit test for it pls?
https://forums.activiti.org/content/sticky-how-write-unit-test

Regards
Martin

Re: JobEntity exception

r3dge — Wed, 25 May 2016 12:14:40 GMT

This problem occurs in production environment and i don't know how to reproduce it.
Asynchronous tasks seems to be involved.

Re: JobEntity exception

r3dge — Wed, 25 May 2016 13:04:18 GMT

I have found a walkaround to retry canceled jobs :

<code>

   List<Job> jobs = pe.getManagementService().createJobQuery().withException().list();

   for(Job job : jobs)
   {
       try {
        if(job.getRetries()<=0){
         System.out.println(job.getId() + " - " + job.getExceptionMessage() + " - " + String.valueOf(job.getRetries()) + " - " + job.getProcessInstanceId() + " - " + job.getProcessDefinitionId());
         pe.getManagementService().executeJob(job.getId());
        }
       }
       catch(ActivitiException ae) {
          ae.printStackTrace();
      }
   }

</code>

However i don't know how to fix that problem…

Re: JobEntity exception

r3dge — Fri, 27 May 2016 10:26:41 GMT

hi,

I guess the problem is fixed.

Two process engines are configured (activiti-explorer and activiti-rest), both working with the same database schema. Jobexecutor and asyncexecutor were enabled on both engines. This configuration generates locks on jobEntity (linked to async serviceTasks) : "JobEntity [id=44142329] was updated by another transaction concurrently".

I changed the configuration like this :

1st engine.properties :

# engine properties
engine.schema.update=false
engine.activate.jobexecutor=false
engine.asyncexecutor.enabled= false
engine.asyncexecutor.activate= false
engine.history.level=full

2nd engine.properties :

# engine properties
engine.schema.update=false
engine.activate.jobexecutor=false
engine.asyncexecutor.enabled=true
engine.asyncexecutor.activate=true
engine.history.level=full

Since this change i didn't get ActivitiOptimisticLockingException ("JobEntity [id=44142329] was updated by another transaction concurrently"). So far so good…

Re: JobEntity exception

jbarrez — Fri, 03 Jun 2016 06:47:59 GMT

Optimistic locking exceptions are not a problem, in fact they are expected when running multiple async executors and are a proof of the logic working correctly.