Bug with concurrentExecution

swamy2156 — Tue, 16 Feb 2016 13:20:48 GMT

Hi,I am using Activiti 5.17 and facing concurrent execution problem in my workflow seems like a activiti bug to me. I am working on a real time scenario like, there will be 8 parallel user tasks attached with boundary timer and service task. I am passing expression to the each service task. All thes

Re: Bug with concurrentExecution

jbarrez — Wed, 17 Feb 2016 12:51:54 GMT

I tested your project, you have a misconfiguration in your logging. The moment I added slf4j-api as a dependency, I could see

01:49:54,706 [pool-1-thread-2] INFO com.uprr.activiti.practice.spring.SimpleServiceTask - This is called from ServiceTask : Service Task3
01:49:54,706 [pool-1-thread-1] INFO com.uprr.activiti.practice.spring.SimpleServiceTask - This is called from ServiceTask : Service Task3

Re: Bug with concurrentExecution

swamy2156 — Wed, 17 Feb 2016 15:49:48 GMT

Thank you Joram for your reply. But, My observation is different and described as follows.

When I run second time by turning ON jobExecutorActivate, I got the following log. If you see first 8 lines printed by pending jobs for previous instance. and last 8 lines are for 2nd process instance. If you see first 2 lines in first set, pool-1-thread-2 & pool-1-thread-1 read same expression and ServiceTask1 form property passed from bpmn model never used. Some times, 3 threads reads same expression though I pass different in service task properties in bpmn. For me, in real time, I am triggering mail from each service task. In this case, instead of ServiceTask1 related mail, I am receiving service task2 mail for twice.

[09:31:21.023]::INFO :ool-1-thread-2::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task2
[09:31:21.023]::INFO :ool-1-thread-1::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task2
[09:31:21.027]::INFO :ool-1-thread-5::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task8
[09:31:21.031]::INFO :ool-1-thread-4::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task7
[09:31:21.041]::INFO :ool-1-thread-3::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task3
[09:31:21.087]::INFO :ool-1-thread-5::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task4
[09:31:21.102]::INFO :ool-1-thread-4::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task5
[09:31:21.114]::INFO :ool-1-thread-2::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task6

[09:31:30.908]::INFO :ool-1-thread-5::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task1
[09:31:30.918]::INFO :ool-1-thread-4::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task2
[09:31:30.931]::INFO :ool-1-thread-2::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task3
[09:31:30.954]::INFO :ool-1-thread-5::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task4
[09:31:30.971]::INFO :ool-1-thread-4::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task5
[09:31:30.990]::INFO :ool-1-thread-2::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task6
[09:31:31.014]::INFO :ool-1-thread-5::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task7
[09:31:31.039]::INFO :ool-1-thread-4::com.uprr.activiti.practice.spring.SimpleServiceTask:16 - This is called from ServiceTask : Service Task8

Can't we use DelegateExpressions with fields in ServiceTasks in parallel flow?

thanks,
swamy.

Re: Bug with concurrentExecution

jbarrez — Wed, 24 Feb 2016 07:55:49 GMT

Not sure I'm following here … but looking at the threads that execute the logic is saying not a lot - maybe it's a thread pool configuration thing, maybe it's a hardware kind of thing.
The easiest would be if you have a unit test that clearly demonstrates the problem you see.

topic Re: Bug with concurrentExecution in Alfresco Archive

Bug with concurrentExecution

Re: Bug with concurrentExecution

Re: Bug with concurrentExecution

Re: Bug with concurrentExecution