| Summary: | timerEvent firing creates extra JoinInstance on a persistent process | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Marian Buenosayres <marianbuenosayres> | ||||
| Component: | jBPM Core | Assignee: | Maciej Swiderski <mswiders> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ivo Bek <ibek> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.0 | ||||||
| Target Milestone: | ER4 | ||||||
| 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:11:38 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: | |||||
| Attachments: |
|
||||||
corrected issue with missing level marker for TimerNodeInstance upon it's completion which caused the join node instance to be created. Committed to both master and 6.0.x Master https://github.com/droolsjbpm/jbpm/commit/9f5a54face7e9757744bac730799b2df9cd14135 6.0.x https://github.com/droolsjbpm/jbpm/commit/bd0f3fe37529aad3b9e214ca4e97eeffc6503fd6 Verified in BPMS 6.0.0.ER4 |
Created attachment 795002 [details] Maven project to test the issue Attached project with JUnit test to see it: A persistent process with two live activities, a workItem and a timerEvent (see attached image The workItem fires, and one side of the execution waits in a safe state in the AND join. When the timer events, the TimerNodeInstance is notified, but it creates another JoinInstance instead of using the existing one. Since it is an AND join, it never continues because one JoinInstance has one incoming connection satisfied, and the other JoinInstance has the other. If this is due to writing my BPMN2 wrong or a configuration, please let me know. I'm pretty sure the process should be valid as is.