[
https://issues.apache.org/activemq/browse/CAMEL-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45212#action_45212
]
Claus Ibsen commented on CAMEL-794:
-----------------------------------
The outstanding issue is when you configure an errorHandler *after* the
*thread*.
{code}
from(xxx)
.thread(2)
.errorHandler(...)
.process(...)
{code}
Then its using the parent errorhandler and if none exists its the default error
handler using DLC with 5 retries.
But setting the errorhandler *before* works as expected:
{code}
from(xxx)
.errorHandler(...)
.thread(2)
.process(...)
{code}
So we gotta figure out how Camel should handle this, and if the *after* should
be supported also.
> 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.
