You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2020/03/10 09:48:00 UTC

[jira] [Updated] (CAMEL-14684) Camel 3.1.0: error handling changed, route no longer stops

     [ https://issues.apache.org/jira/browse/CAMEL-14684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated CAMEL-14684:
------------------------------------
    Attachment: BodyOnlyAggregationStrategyTest.java

> Camel 3.1.0: error handling changed, route no longer stops
> ----------------------------------------------------------
>
>                 Key: CAMEL-14684
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14684
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 3.1.0
>            Reporter: Remco Schoen
>            Assignee: Guillaume Nodet
>            Priority: Critical
>         Attachments: BodyOnlyAggregationStrategy.groovy, BodyOnlyAggregationStrategyTest.groovy, BodyOnlyAggregationStrategyTest.java
>
>
> Hi,
> I noticed that the error handling has changed in 3.1.0 from 3.0.1. We use a DeadLetterChannel and when the error has been handled, I expect the original route to stop and not to continue.
> When we use enrich we pass the exchange property CamelErrorHandlerHandled back to ensure the calling route stops, but that has changed. Is this correct and should we change our aggregation strategy?
> I added the strategy and it’s test.
> Kind regards,
> Remco Schoen



--
This message was sent by Atlassian Jira
(v8.3.4#803005)