You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/12/08 20:22:00 UTC

[jira] [Commented] (CAMEL-17296) Multicast option stopOnAggregateException has no effect

    [ https://issues.apache.org/jira/browse/CAMEL-17296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17455974#comment-17455974 ] 

Claus Ibsen commented on CAMEL-17296:
-------------------------------------

Yeah Karen you are welcome to deprecate the option, and add a note in the 3.14 upgrade guide, and then we can remove the option in 3.15.

> Multicast option stopOnAggregateException has no effect
> -------------------------------------------------------
>
>                 Key: CAMEL-17296
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17296
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 3.13.0
>            Reporter: Karen Lease
>            Priority: Minor
>             Fix For: 3.15.0
>
>
> The option stopOnAggregateException has no effect. This was added in CAMEL-10272, but since Camel 3.0, the MulticastProcessor method isStopOnAggregateException is no longer called. If any exception is caught in an aggregation strategy, it is set on the original Exchange object and the processing is terminated, whether this option is set or not.
> If the option is obsolete, it should be removed and the documentation and test cases should be updated.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)