Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-12648

ExchangeSentEvent not fired if no EventNotifier is accepting ExchangeSendingEvent

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not A Problem
    • 2.20.0, 2.21.0, 2.22.0
    • 2.23.0
    • camel-core
    • None
    • Unknown

    Description

      Due to changes in CAMEL-11346, many processors (including SendProcessor) no longer send ExchangeSentEvent when processing is done. The StopWatch object is not created when EventHelper.notifyExchangeSending returns false. If no EventNotifier is registered to receive that event, it will be false. But an EventNotifier may still be registered to receive ExchangeSentEvent. The StopWatch should be created when there is an EventNotifier registered for ExchangeSentEvent even when ExchangeSendingEvent is not, unless those events are always required to be paired together.

      Attachments

        Activity

          People

            davsclaus Claus Ibsen
            kgarner Kevin Garner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: