Red Hat Bugzilla – Bug 803692
Converging exclusive gateway does not work according to documentation
Last modified: 2012-05-03 23:48:52 EDT
Description of problem:
Documentation chapter 5.6.2:
...XOR or exclusive means that it continues as soon as one of its incoming branches has been completed. If it is triggered from more than one incoming connection, it will trigger the next node for each of those triggers.
Following reproducer shows that after the first triggering of converging XOR gateway no more tokens go through it:
1. 2 of 3 outgoing flows from OR gateway have satisfied their condition.
2. First path (script1) is taken and converging XOR gateway is triggered.
3. Final script task and end node is triggered.
4. Second path (script2) is taken, but XOR gateway is not triggered.
Here is a pull request with the reproducer, check also console output:
The issue was not with the converging XOR gateway, but with the inclusive diverging gateway, that wasn't creating all node instances that will be triggered before triggering the first one, leading to an early implicit termination of the process instance.
Update status to ON_QA. Please verify them against ER6.