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 2016/04/25 19:57:13 UTC
[jira] [Commented] (CAMEL-9293) Inconsistent Behavior in Split
Exception Handling
[ https://issues.apache.org/jira/browse/CAMEL-9293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256692#comment-15256692 ]
Claus Ibsen commented on CAMEL-9293:
------------------------------------
You need to use continued(true) if you want to continue routing. When using handled(true) the exchange should not be routed after the splitter, as there was an exception during the splitting and it was handled, but then routing should break out.
> Inconsistent Behavior in Split Exception Handling
> -------------------------------------------------
>
> Key: CAMEL-9293
> URL: https://issues.apache.org/jira/browse/CAMEL-9293
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.16.0
> Reporter: Srinivas Badveli
> Attachments: SplitExceptionHandlingTest.java
>
>
> If the first item in Split Processing throws an Exception, the aggregated exchange it not being sent to next processor available. If the item is not the first, then the aggregated exchange is sent to next processor. In either case the exception was marked as handled in onException process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)