[
https://issues.apache.org/activemq/browse/CAMEL-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45497#action_45497
]
Bela Vizy commented on CAMEL-794:
---------------------------------
There's only one issue with this, but isn't a big deal. The failure gets logged
twice. Once for the thread(n) and once for the processor which failed somewhere
after the thread(n). They get logged with their respective exchanges. I think
only the exchange before the failed processor should be logged.
I will try to create a test case, but not sure how can this be automated with
JUnit (you have to set it to debug and watch the log).
Anyway this is not a showstopper bug.
> Pipeline with thread() processor also redelivers following the default policy
> independently from the preset errorhadling
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-794
> URL: https://issues.apache.org/activemq/browse/CAMEL-794
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.4.0
> Reporter: Bela Vizy
> Assignee: Claus Ibsen
> Fix For: 1.5.0
>
> Attachments: BelasThreadErrorHandlerTest1.java,
> BelasThreadErrorHandlerTest2.java
>
>
> When using the thread processor in a simple pipeline, the exchange will be
> redelivered 6 times (default policy) along with the preset errorhandler
> settings. The code below will re-deliver 6 times to the default
> DeadLetterChannel and once to the log:errorTester.
>
> errorHandler(deadLetterChannel("log:errorTester?level=ERROR").maximumRedeliveries(1));
>
> from("seda:whatEver")
> .thread(2)
> .process(new Processor() {
> public void process(Exchange exchange) throws Exception
> {
> System.out.println("### Exchg : " +
> exchange.getExchangeId());
> throw new Exception("Kaboom 2!");
> }
> });
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
