[
https://issues.apache.org/activemq/browse/CAMEL-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51296#action_51296
]
Claus Ibsen commented on CAMEL-1546:
------------------------------------
Frank
I had a "sleep" on this (actually a walk with the dog) and my suspicion is that
the error handler is not wrapped around each child output in the aggregator.
So whenever an exception occurs its propagated back to the aggregator (based on
batch processor) that has this (flaw/feature) that it swallows exceptions.
So when you split the route into a sub route outside the aggreagator then the
error handler is intercepted as expected.
The remedy is pobably to ensure the logic that applies the error handler also
can handle the aggregator and its children as well.
> Exception handler is not applied for aggregate component
> --------------------------------------------------------
>
> Key: CAMEL-1546
> URL: https://issues.apache.org/activemq/browse/CAMEL-1546
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0-M1
> Reporter: Frank Schwarz
>
> <camelContext xmlns="http://camel.apache.org/schema/spring";>
> <onException>
> <exception>java.lang.Exception</exception>
> <!-- no retry, just dump the error -->
> <handled><constant>true</constant></handled>
> <convertBodyTo type="java.lang.String" />
> <to uri="bean:ErrorMessageTransformProcessor" />
> <to uri="freemarker:error.ftl" />
> <to uri="file:///C:/temp/camel/err" />
> </onException>
> ...
> <route>
> <from uri="jms:queue:InQueue"/>
> <aggregate batchTimeout="5000"
> strategyRef="MyAggregationStrategy">
> <correlationExpression>
> <header>MyCorrelationId</header>
> </correlationExpression>
> <to uri="bean:AggregatedItemsTransformProcessor" /> ***
> <to uri="jms:queue:OutQueue" />
> </aggregate>
> </route>
> </camel>
> If in the bean *** occurs an exception, nothing happens. Debugging shows that
> the exception handler is not triggered. Nothing is logged.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
