Activiti reates multiple tasks

[plehal]

I have this workflow in production since 2012. However, recently it started behaving little weird. At completion of certain tasks,  it creates instances of multi-user tasks twice or thrice there by creating each task two or three times. What can cause it? I tried to submit this issue a few month ago but the forum was not functional.

[jbarrez]

What has changed? Did you upgrade to a newer version? Something must have changed …

Is it consistently doing that? Or just sometimes?

[plehal]

The only thing that has changed is the  OS upgrade from Fedora 14 to Fedora 22 and implied Database (MySQL upgrade).  It used to manifest this before too but very rare(<0.5% and could be ignored). Now it is happening  more(2-3%). I am trying to analyse from higher level about the cause of this behavior. For that I need to understand how multiuser tasks are created. It is showing more  at the creation of a multiuser task which follows another  gateway after a multiuser task(as shown in the attached file-change the extension to png from txt). Vector for creating the multiuser task is created from a database query which is always the same. What might cause the m-usertask to be created multiple times with the same vector? Is there signal after the creation of a task to the engine that it has been created that is not getting relayed in time? Please, help. I am using 5.12.

[plehal]

As I mentioned previously, it happens randomly  but frequency has increased now. Still there is no clear consistency which can point to some smoking gun.

[martin_grofcik]

Hi Parm,

For that I need to understand how multiuser tasks are created.

org.activiti.engine.impl.bpmn.behavior.MultiInstanceActivityBehavior
Regards
Martin

[plehal]

That turned out a dead-end lead. However, I noticed that I was able to delete extra tasks which should not normally happen as mentioned here.

https://forums.activiti.org/content/need-info-deleting-task


any other possibilities??

[plehal]

Wondering how the next task is created when one task is completed. Is it part of the same execution or total separate process in the engine somewhere else. In that case, can two instances of engine recreate the issue when one task is complete and both instances try to move the process forward. I understand that there should be only one engine but just trying to figure out what is going on. Also, if next tasks are created by the engine process then is there any way to pause/stop/delay that anywhere in the engine instantiation?