Red Hat Bugzilla – Bug 994373
jBPM engine does not support multiple incoming flow into end event node
Last modified: 2014-08-06 16:07:02 EDT
Created attachment 783693 [details]
Take a look at the attached process definition. It was created and validated in jBPM Designer - and as far as I know it's a valid bpmn2 definition. However, when I tried to build a project containing this definition, exception appeared in the server log (attaching the stacktrace).
Created attachment 783694 [details]
Note that support for multiple incoming our outgoing connections for all nodes other than gateways are currently not supported (as best practice). Support for multiple connections can be enabled however using system parameter: -Djbpm.enable.multi.con=true
See also https://issues.jboss.org/browse/JBPM-3372
Could you verify this issue still exists when using that parameter?
Tiho, would it be possible to have designer validate processes taking this system parameter into account (so signaling process definitions with multiple incoming / outgoing connections as invalid if this parameter is not set to true)?
I can see the problem even when using the property - see the pull request https://github.com/droolsjbpm/jbpm/pull/176
EndNode does not check the property to allow multiple incoming connection, I'll fix it
Committed to master and 6.0.x branch:
Verified on BPMS 6.0.0.ER2
*** Bug 975935 has been marked as a duplicate of this bug. ***
qe_test_coverage: covered by community unit tests