[
https://issues.apache.org/jira/browse/CAMEL-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hokutor closed CAMEL-16598.
---------------------------
Resolution: Fixed
> Blog about multicast's exception routing behavior on encountering exception
> ---------------------------------------------------------------------------
>
> Key: CAMEL-16598
> URL: https://issues.apache.org/jira/browse/CAMEL-16598
> Project: Camel
> Issue Type: Wish
> Components: documentation, eip
> Reporter: Hokutor
> Priority: Minor
> Fix For: 3.x
>
>
> 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
> # Exception was encountered in first aggregated child exchange (vs.)
> # 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.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
