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

Blog about multicast's exception routing behavior on encountering exception

    XMLWordPrintableJSON

    Details

    • Type: Wish
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.x
    • Component/s: documentation, eip
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      This is w.r.t [discussion here](https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Multicast.20behavior.20differences.20based.20on.20First.20Merging.20Branch/near/238173160)

      The implementation of aggregator in multicast EIP has significant impact on how the routing continues for the remaining flow when    

      1. Exception was encountered in first aggregated child exchange (vs.)
      2. Exception was encountered in remaining child exchanges

       

      As a camel user, it took us by surprise until we ran debuggers and noticed certain state set on exchange becomes a major [decision maker](https://github.com/apache/camel/blob/6dff85675e9b73e8a528bc2683935ec3c1ed26b7/core/camel-core-processor/src/main/java/org/apache/camel/processor/PipelineHelper.java#L43-L44) on further routing of the aggregated exchange.

      It would be beneficial to have this blogged on camel website for any other users who might hit upon this in future.

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              hokutor Hokutor
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: