Bug 803692

Summary: Converging exclusive gateway does not work according to documentation
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Radovan Synek <rsynek>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: VERIFIED --- QA Contact: Radovan Synek <rsynek>
Severity: medium Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GACC: lpetrovi
Target Milestone: ---   
Target Release: BRMS 5.3.0.GA   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Radovan Synek 2012-03-15 12:40:24 UTC 
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:
https://github.com/droolsjbpm/jbpm/pull/56
commit:
https://github.com/rsynek/jbpm/commit/5b4d87a4c36751ae1a5c8357ab8660d437dd2a0a
Comment 2 Kris Verlaenen 2012-04-11 16:04:23 UTC 
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.
Comment 3 Ryan Zhang 2012-04-23 07:37:15 UTC 
Update status to ON_QA. Please verify them against ER6.