topic Re: concurrent execution with exclusive job in Alfresco Archive

concurrent execution with exclusive job

larswillrich — Fri, 01 Mar 2013 11:00:51 GMT

hello,i've got this situation:[img]http://s1.directupload.net/images/130301/v3hm273e.jpg[/img]Service-Call: async=false, exclusive-job=trueT1_1, T5_1, T2_2, T3_2Service-Call: async=true, exclusive-job=falseT2_1, T3_1with org.activiti.spring.SpringProcessEngineConfiguration -> jobExecutorActivate=

Re: concurrent execution with exclusive job

frederikherema1 — Fri, 01 Mar 2013 11:05:31 GMT

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

The "exclusive-job=true" makes no sense when the activity is not async. The T2_2 will run right after T2_1 in the same thread. As will T3_2 run right after T3_1. Set the async=true on the *_2 tasks and your issue will be fixed.

Re: concurrent execution with exclusive job

larswillrich — Fri, 01 Mar 2013 11:39:47 GMT

The "exclusive-job=true" makes no sense when the activity is not async.

i thought, exclusive-job=true set as default, if its not explicit declared or the async-attribute is set false?

Re: concurrent execution with exclusive job

jbarrez — Fri, 01 Mar 2013 18:27:24 GMT

Exclusive job = true has only meaning when executing things async. But I can see your point. Tijs has written down some things about it: http://bpmn20inaction.blogspot.be/2012/12/implement-parallel-execution-in-activiti.html

What happens if you make them all async and exclusive?

Re: concurrent execution with exclusive job

larswillrich — Sat, 02 Mar 2013 09:01:15 GMT

What happens if you make them all async and exclusive?

all: async and exclusive=true
Then, of course all activities will run sequential (but i want to run T2_1 and T3_1 in parallel)

all activities without T2_1 and T3_1: async=false
T2_1 and T3_1: async = true, exclusive = false
Then, it will throw the ActivitiOptimisticLockingException.

solution:
T1,T4: async = false
T2_1, T3_1: async = true, exclusive = false
T2_2, T3_2: async = true, exclusive = true

Then, T2_1 and T3_1 execute in parallel and after that, it runs sequential again.
Thats the solution for my problem.
Thanks.

regards
Lars

Re: concurrent execution with exclusive job

badrisudheer — Fri, 26 Apr 2013 17:21:51 GMT

Just a small question - if there is a sub-process (using CallActivity) embedded in a Process definition and on that sub-process, keeping async=false, will there be any difference setting exclusive as false or true ?

Re: concurrent execution with exclusive job

trademak — Mon, 29 Apr 2013 12:08:47 GMT

No, exclusive only has meaning when async=true

Best regards,

Re: concurrent execution with exclusive job

badrisudheer — Mon, 29 Apr 2013 13:14:33 GMT

Thanks for the quick reply. The behavior I am trying to understand is - Created a Process Definition with 2 simple Service Tasks & 2 Sub Process (Using CallActivity) and each Sub Process has a Receive Task with a Timer Boundary on it. In this scenario, when the signal is issued on the first Timer Task - the process resumes and continues and when it is about to invoke the Timer in 2nd Sub Process in sequence, it is throwing ActivitiOptimisticLocking Exception on Timer Entity of first SubProcess and the process instance is getting rolled back to the first Time Entity. Trying to understand why this is happening.

Re: concurrent execution with exclusive job

jbarrez — Tue, 30 Apr 2013 09:11:45 GMT

Do you have a simple process that demonstrates the problem?