Bug 994373
| Summary: | jBPM engine does not support multiple incoming flow into end event node | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Radovan Synek <rsynek> | ||||||
| Component: | jBPM Core | Assignee: | Maciej Swiderski <mswiders> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Radovan Synek <rsynek> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.0.0 | CC: | mswiders, rzhang, smala | ||||||
| Target Milestone: | ER2 | ||||||||
| Target Release: | 6.0.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-08-06 20:07:02 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 783694 [details]
error stacktrace
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: https://github.com/droolsjbpm/jbpm/commit/b2d07c05dfb8d8312791034f424c4e6f0b36f6c5 https://github.com/droolsjbpm/jbpm/commit/f8f310dbd9fd2454a2783033e4a6a7434176ab2f 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 |
Created attachment 783693 [details] process definition 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).