Completing any join activity obsoletes other active activities in Nested Fork/Join Workflow
I am using JBPM4.4. I have attached a workflow, which I am using.
In given workflow I am using multiple forks and joins.
At time when activity14, activty15, activity16 and acivtiy17 are active, completing any one activity marks rest other activities obsolete. In case I am completing activity14 then it should only mark activity15 obsolete not activity16 and activity17.
It is trying to handle join’s dangling nodes. But finds all active nodes as dangling nodes.
Analysis: I looked at JoinActivity implementation. To get dangling nodes code is written to get all executions of current parent. Which gives all active nodes.
Do I need to handle in different way to get expected result? Or it’s issue with JBPM4.4?
Let me know in case more info needed. Any help appricated.