Hi Silvio
We rely on the relased 4.4 and we have comparable problem:
- 2 branches fork/join works fine without specifying the multiplicity attribute
- 2 branches fork/join with multiplicity = 1 leave the unjoinded branch as a normal executing task while the joined execution goes on. What is wrong is that THERE EXIST 2 executions after the join.
I aggree with you, this is abnormal and I can confirm it exists on the JBPM 4.4 release, and has be reported elswhere.
I do not see why Ronald thought about a kill flag. In any case a not joined execution should be set to state END or inactive or killed. It should not remain active because this lead to uncorrect implementation of the JPDL join semantic. Maybe also this has to do with the time people thought about using this multiplicity attribute to deal the JPDL for/loop semantic...
Thanks for your patch, I will take a look at it, but I'm not the expected expert and we might need some additional help on this question.
Regards
JeanNo Helal