AnsweredAssumed Answered

concurrent execution with exclusive job

Question asked by larswillrich on Mar 1, 2013
Latest reply on Apr 29, 2013 by badrisudheer
hello,

i've got this situation:

[img]http://s1.directupload.net/images/130301/v3hm273e.jpg[/img]

Service-Call: async=false, exclusive-job=true
T1_1, T5_1, T2_2, T3_2

Service-Call: async=true, exclusive-job=false
T2_1, T3_1

with org.activiti.spring.SpringProcessEngineConfiguration -> jobExecutorActivate=true


i thought, that would solve the problem with the throwing ActivitiOptimisticLockingException ;)

now I've got the following behavior:

T2_1 and T3_1 are executed in parallel
But then, T2_2 and T3_2 are executed also in parallel (what i do not understand), although exclusive-job is set true

i thought, when exclusive-job is set true, the activity would not be execute in parallel in the same process instance, as i read here:
http://www.activiti.org/userguide/index.html#exclusiveJobs

Since Activiti 5.9, the JobExecutor makes sure that jobs from a single process instance are never executed concurrently.

It would be nice if someone could explain the behavior.

Thanks in advance
Lars Willrich

Outcomes