cancel
Showing results for 
Search instead for 
Did you mean: 

Multi executions (jobs) of timerIntermediateCatchevent in a process

kse
Champ in-the-making
Champ in-the-making
Hello Support,

Actually I encounter a problem in a workflow using a timer catching event.
At some point, I notice more than one executions of this timer for a single process instance.  
Do you have an idea ?
Is it a well-known problem ? Or Is it a design mistake ?
Should I do differently ?

Below the part of my workflow where I encounter a problem :

http://forums.activiti.org/sites/activiti_forums/files/timerCatchingEvent.txt

Extract of ACT_RU_EXECUTION :

http://forums.activiti.org/sites/activiti_forums/files/ACT_RU_EXECUTION.txt

Extract of ACT_RU_JOB :

http://forums.activiti.org/sites/activiti_forums/files/ACT_RU_JOB.txt

Extract of ACT_HI_ACTINST :

http://forums.activiti.org/sites/activiti_forums/files/ACT_HI_ACTINST.txt

Thank you in advance for your efforts to answer,

Sophian
5 REPLIES 5

trademak
Star Contributor
Star Contributor
Do you know if the intermediate timer event was also started multiple times? Because in your process definition I see a possible loop.

Best regards,

kse
Champ in-the-making
Champ in-the-making
Unfortunately, I have no more information than those extracts.
I only notice that there are two executions when duration (10 min) of the timer is completed. (see Extract of ACT_HI_ACTINST at 9 am)
But when a loop may happen ?
A few days earlier there was much more executions for a single process instance, about 1500 !

Thank you in advance,

Sophian

trademak
Star Contributor
Star Contributor
We would need more info to understand a possible cause of this behavior.
Is the service task executing taking really long for example (>1 min)?

Best regards,

kse
Champ in-the-making
Champ in-the-making
The service task never take more than 1sec to complete.
On the attachment ACT_HI_ACTINST.txt, the extract of ACT_HI_ACTINST table we could see that the second execution of the same service task was started before the end of the first.

First execution of the Service task :
- START_TIME -> 09:10:32:921000 ; END_TIME -> <b>09:10:33:796000</b> ; DURATION : 875ms
Second execution of the Service task for the same process instance :
- START_TIME -> <b>09:10:33:437000</b> ; END_TIME -> 09:10:34:030000 ; DURATION : 593ms

Best regards,

Sophian

trademak
Star Contributor
Star Contributor
It would be great if you could create a unit test project showing the issue. That would make it easier for us to dive into the problem.

Best regards,