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

Custom HistoryEventHandler automatically wrapped by CompositeDbHistoryEventHandler

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: None
    • Icon: L3 - Default L3 - Default
    • None
    • 7.13.0
    • spring-boot
    • 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

            Miklas Boskamp added a comment -

            Hi p.mutser,

            thanks for raising this issue. I found that with CAM-10650 we fixed a bug in the SpringBootStarter related to custom HistoryEventHandlers. Related to that a new ProcessEngineConfiguration property was introduced in CAM-11217. Please have a look here. Additionally you can read up on the new property in the docs.

            I hope this information helped you resolve the issue. Have a great weekend!
            Cheers,
            Miklas

            Miklas Boskamp added a comment - Hi p.mutser , thanks for raising this issue. I found that with CAM-10650 we fixed a bug in the SpringBootStarter related to custom HistoryEventHandlers. Related to that a new ProcessEngineConfiguration property was introduced in CAM-11217 . Please have a look here . Additionally you can read up on the new property in the docs . I hope this information helped you resolve the issue. Have a great weekend! Cheers, Miklas

            Paul Mutser added a comment - - edited

            Thanks, this indeed allowed us to resolve the issue.

            I hope you will also be updating the docs I linked to, so it is consistent with the new behaviour
            (maybe put a remark about this in the 7.13 release notes as well)

            Paul Mutser added a comment - - edited Thanks, this indeed allowed us to resolve the issue. I hope you will also be updating the docs I linked to, so it is consistent with the new behaviour (maybe put a remark about this in the 7.13 release notes as well)

            Miklas Boskamp added a comment -

            Hey p.mutser,

            great to hear that you were able to resolve the problem. I agree that this should be documented more clearly. I have created CAM-12722 to take care of it.
            I will close this ticket.
            Thank you for your feedback.
            Cheers,
            Miklas

            Miklas Boskamp added a comment - Hey p.mutser , great to hear that you were able to resolve the problem. I agree that this should be documented more clearly. I have created CAM-12722 to take care of it. I will close this ticket. Thank you for your feedback. Cheers, Miklas

              miklas.boskamp Miklas Boskamp
              p.mutser Paul Mutser
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: