AnsweredAssumed Answered

Async service tasks fails to update status

Question asked by paulfrancis on Apr 24, 2014
Latest reply on Apr 28, 2014 by martin.grofcik
I executed an activiti model, made up of 13 asynchronous non exclusive java service tasks, all in parallel to one another, and all linked to a single start and end event.

When the workflow starts, all the 13 service tasks gets instantiated, and the task execution completes successfully for all 13 on the back end (python scripts which produces 13 different images) , however when checked the activiti database, it shows only 5 of them were completed successfully and the rest of 8 scheduled for retry.

When retry happens all 8 remaining tasks are  re-executed successfully in the back end (produced 8 images), but again activiti counts only 4 of them completed successfully and the rest  4 scheduled for retry. The final retry executes all four both in the front and back end.

there is a total of 25 executions instead of 13.

I cannot explain this behavior of activiti, such as even though the java delegate class executes successfully in parallel, its not registering the exit of some of the async-non-exclusive tasks.

Please help me out in understanding this strange behavior.


Outcomes