4 Replies Latest reply on Jan 9, 2010 2:06 PM by kukeltje

    [jbpm4.3] Strange behavior with join multiplicity="1"

    markroy

      I'm seeing some strange behavior when using join with multiplicity="1". I've created a test case (attached). The test forks two paths, each containing one task followed by the join. There's an additional task following the join. The test case completes both of the forked tasks. If you remove the multiplicity attribute from the join, the test runs correctly. However, with join multiplicity="1", the forked executions do not seem to be ended and I end up with *two* instances of the post-join task.

       

      Can anyone shed any light on this?