Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-1733

Interrupting event subprocess does not cancel event subscriptions & timers

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.1.0, 7.1.0-alpha2
    • Component/s: engine
    • Labels:
      None

      Description

      #Problem Description

      The BPMN Spec mandates that if an Interrupting event subprocess fires, it must make sure that other event subprocesses do not fire as well.

      Reproduce:

      • Create process with two interrupting event subprocesses: one waiting for a message and one waiting for a signal
      • Place user task afterm message start event of first event subprocess
      • Start process
      • Trigger message event subprocess by delivering the message. As a result the process instance is waiting in the user task after the event subprocess

      => If I send the signal now, the second event subprocess triggers. This should not be possible.

      The same problem can be experienced with timer events

        Attachments

          Activity

            People

            Assignee:
            sebastian.menski Sebastian Menski
            Reporter:
            meyer Daniel Meyer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: