-
Bug Report
-
Resolution: None
-
L3 - Default
-
None
-
7.13.0
-
None
According to docs https://docs.camunda.org/manual/7.13/user-guide/process-engine/history/#provide-a-custom-history-backend when implementing a custom HistoryEventHandler, the default DbHistoryEventHandler gets disabled.
In version 7.10, this was the behaviour. Only our own custom HistoryEventHandler was active.
Since upgrading to 7.13, our own handler automatically gets wrapped inside a CompositeDbHistoryEventHandler, causing the DbHistoryEventHandler to still be active.
This is unwanted behaviour, and in contradiction to the docs.
Observation:
Run processEngineConfiguration.getHistoryEventHandler()
7.10 result:
<our own historyEventHandler class>
7.13 result:
org.camunda.bpm.engine.impl.history.handler.CompositeDbHistoryEventHandler
This is the controller panel for Smart Panels app
[CAM-12716] Custom HistoryEventHandler automatically wrapped by CompositeDbHistoryEventHandler
| Mentioned Roles |
| Mentioned Groups |
| Assignee | New: Miklas Boskamp [ miklas.boskamp ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Description |
Original:
According to docs [https://docs.camunda.org/manual/7.13/user-guide/process-engine/history/#provide-a-custom-history-backend|https://docs.camunda.org/manual/7.13/user-guide/process-engine/history/#provide-a-custom-history-backend,] when implementing a custom HistoryEventHandler, the default DbHistoryEventHandler gets disabled.
In version 7.10, this was the behaviour. Only our own custom HistoryEventHandler was active. Since upgrading to 7.13, our own handler automatically gets wrapped inside a CompositeDbHistoryEventHandler, causing the DbHistoryEventHandler to still be active. This is unwanted behaviour, and in contradiction to the docs. h3. Observation: Run {{processEngineConfiguration.getHistoryEventHandler()}} 7.10 result: <our own historyEventHandler class> 7.13 result: {{org.camunda.bpm.engine.impl.history.handler.CompositeDbHistoryEventHandler}} |
New:
According to docs [https://docs.camunda.org/manual/7.13/user-guide/process-engine/history/#provide-a-custom-history-backend|https://docs.camunda.org/manual/7.13/user-guide/process-engine/history/#provide-a-custom-history-backend] when implementing a custom HistoryEventHandler, the default DbHistoryEventHandler gets disabled.
In version 7.10, this was the behaviour. Only our own custom HistoryEventHandler was active. Since upgrading to 7.13, our own handler automatically gets wrapped inside a CompositeDbHistoryEventHandler, causing the DbHistoryEventHandler to still be active. This is unwanted behaviour, and in contradiction to the docs. h3. Observation: Run {{processEngineConfiguration.getHistoryEventHandler()}} 7.10 result: <our own historyEventHandler class> 7.13 result: {{org.camunda.bpm.engine.impl.history.handler.CompositeDbHistoryEventHandler}} |
| Mentioned Roles |
| Mentioned Groups |
| Mentioned Roles |
| Mentioned Groups |
| Mentioned Roles |
| Mentioned Groups |