AnsweredAssumed Answered

Wrong script task listener executed

Question asked by rwa on Jan 29, 2016
Latest reply on Mar 11, 2016 by behemot
Hi,

We face a really annoying bug with activiti.

We use version 5.13 of activiti.

Here is the bug scenario (see bpmn here: https://drive.google.com/file/d/0BxxZafFzNUQdV1JGSnRUZ242SnM/view?usp=sharing for activity references) :
The process instance is in the usertask31 activity. The user does action for going out of this task and going into servicetask1.
This causes an error that says : "No outgoing sequence flow of the exclusive gateway 'exclusivegateway35' could be selected for continuing the process".
The bug appears randomly. When the bug occurs, a restart of alfresco resolves the problem.

After some analysis and adding some logs in activiti engine code, we found that in fact a wrong listener seems to be executed : The complete-event listener attached to task usertask23 is executed instead of the complete-event listener of task usertask31.

Our listeners are implemented by alfresco script task listener (org.alfresco.repo.workflow.activiti.tasklistener.ScriptTaskListener).

We check forums and activiti release notes about such a bug but with no result.

Do you have any idea about this bug ?
Do you think that a wrong task-listener association could be done (randomly!) ?

Outcomes