[
https://issues.apache.org/jira/browse/CAMEL-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503195#comment-13503195
]
C S commented on CAMEL-3394:
----------------------------
{code}
Can it be that the issue here is back since version 2.9.4?
The following route works ok in camel 2.9.3 -> if an exception is thrown by
body.list the errorhandler kicks in and the
message is handled by "direct:errorhandler". Since 2.9.4 (and also with the
latest version, 2.10.2) the errorhandler is no longer
active.
from("direct:sampleUri")
.errorHandler(deadLetterChannel("direct:errorhandler").disableRedelivery())
.multicast()
.stopOnException()
.split(simple("${body.list}"))
.streaming()
.stopOnException()
.process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
}
}).end()
.end()
.to("direct:somewhere_else_1")
.to("direct:somewhere_else_2")
.end();
{code}
> Splitter and Multicast EIP marks exchange as exhausted to early if exception
> was thrown from an evaluation
> ----------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3394
> URL: https://issues.apache.org/jira/browse/CAMEL-3394
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.5.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Cannot-handle-Exception-thrown-from-Splitter-Expression-tp3286043p3286043.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
