-
Bug Report
-
Resolution: Duplicate
-
L3 - Default
-
None
-
7.13.0, 7.14.0, spring-boot 3.4.4
-
None
org.camunda.bpm.spring.boot.starter.event.PublishDelegateParseListener doesn't check if execution listener is already added to the given activity.
It leads that execution listener is added several times for one activity with boundary events.
Here in the debugger you case see all listeneres added to "Test Task":
This is the controller panel for Smart Panels app
[CAM-12868] EventPublisherPlugin adds execution listener twice on activity with boundary event
Description |
Original:
org.camunda.bpm.spring.boot.starter.event.PublishDelegateParseListener doesn't check if execution listener is already added to the given activity.
It leads that execution listener is added several times for one activity with boundary events. Example affected process: Example: |
New:
org.camunda.bpm.spring.boot.starter.event.PublishDelegateParseListener doesn't check if execution listener is already added to the given activity.
It leads that execution listener is added several times for one activity with boundary events. Example of affected process: !process-boundary-event.png|thumbnail! Example: |
Mentioned Roles |
Mentioned Groups |
Description |
Original:
org.camunda.bpm.spring.boot.starter.event.PublishDelegateParseListener doesn't check if execution listener is already added to the given activity.
It leads that execution listener is added several times for one activity with boundary events. Example of affected process: !process-boundary-event.png|thumbnail! Example: |
New:
org.camunda.bpm.spring.boot.starter.event.PublishDelegateParseListener doesn't check if execution listener is already added to the given activity.
It leads that execution listener is added several times for one activity with boundary events. Example of affected process: !process-boundary-event.png|thumbnail! Here in the debugger you case see all listeneres added to "Test Task": !debug.png|width=720,height=493,thumbnail! |
Mentioned Roles |
Mentioned Groups |
Description |
Original:
org.camunda.bpm.spring.boot.starter.event.PublishDelegateParseListener doesn't check if execution listener is already added to the given activity.
It leads that execution listener is added several times for one activity with boundary events. Example of affected process: !process-boundary-event.png|thumbnail! Here in the debugger you case see all listeneres added to "Test Task": !debug.png|width=720,height=493,thumbnail! |
New:
org.camunda.bpm.spring.boot.starter.event.PublishDelegateParseListener doesn't check if execution listener is already added to the given activity.
It leads that execution listener is added several times for one activity with boundary events. Example of affected process: !process-boundary-event.png|thumbnail! Here in the debugger you case see all listeneres added to "Test Task": !debug.png|width=231,height=158,thumbnail! |
Mentioned Roles |
Mentioned Groups |