[CAM-6359] Execution listener is executed more than once if it triggers execution tree compaction/expansion Created: 04/Jul/16  Updated: 11/Aug/16  Resolved: 07/Jul/16

Status: Closed
Project: camunda BPM
Component/s: engine
Affects Version/s: None
Fix Version/s: 7.6.0, 7.5.3, 7.6.0-alpha3

Type: Bug Report Priority: L3 - Default
Reporter: Deivarayan Azhagappan Assignee: Thorben Lindhauer
Resolution: Fixed Votes: 0
Labels: SUPPORT
Remaining Estimate: 0 minutes
Time Spent: Not Specified
Original Estimate: 0 minutes

Attachments: File MultipleExecutionListenerCall.bpmn    
Issue Links:
Depedendency

 Description   

Problem description:
An execution listener is executed multiple times when the delegation code triggers execution tree expansion/compaction. For example, when a service task sends a BPMN message to a boundary event of a user task in the another concurrent execution. This ends the other concurrent execution and triggers execution tree compaction.

Reason:

  • Executions have a property listenerIndex that stores which listeners have already been invoked. If the current execution is replaced by another execution, this index is not passed over, so the listener invocations in the context of the replacing execution start at 0 again.

Generated at Mon Oct 23 17:26:28 CEST 2017 using JIRA 6.4.6#64021-sha1:33e5b454af4594f54560ac233c30a6e00459507e.