Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-4119

timerEvent firing creates extra JoinInstance on a persistent process

    Details

    • Steps to Reproduce:
      Hide

      run "mvn package" on the attached project

      Show
      run "mvn package" on the attached project

      Description

      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.

        Gliffy Diagrams

          Attachments

          1. possible_bug.bpmn2
            17 kB
          2. possible_bug.png
            possible_bug.png
            23 kB
          3. possible_bug.tar.gz
            31 kB

            Activity

              People

              • Assignee:
                marco.rietveld Marco Rietveld
                Reporter:
                marianbuenosayres Mariano Nicolas De Maio
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: