[CAM-1733] Interrupting event subprocess does not cancel event subscriptions & timers

#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

Daniel Meyer created issue - 18/Jan/14 12:55 PM

Daniel Meyer made changes - 18/Jan/14 12:55 PM

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Daniel Meyer made changes - 18/Jan/14 12:55 PM

Assignee

New: Roman Smirnov [ smirnov ]

Roman Smirnov made changes - 20/Jan/14 2:31 PM

Assignee	Original: Roman Smirnov [ smirnov ]	New: Sebastian Menski [ sebastian.menski ]
Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Resolved [ 5 ]
Remaining Estimate		New: 0 minutes [ 0 ]
Original Estimate		New: 0 minutes [ 0 ]

Sebastian Menski made changes - 20/Jan/14 5:08 PM

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

Robert Gimbel made changes - 31/Jan/14 12:17 PM

Fix Version/s

New: 7.1.0-alpha2 [ 13190 ]

Thorben Lindhauer made changes - 14/Feb/19 2:55 PM

Workflow

Original: camunda BPM [ 25755 ]

New: Backup_camunda BPM [ 58243 ]

camunda BPM