Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Tue, 9 Dec 2014 10:23:12 +0000 (UTC)
From: "metatech (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12760393.1418115678000.108270.1418120592500@Atlassian.JIRA>
In-Reply-To: <JIRA.12760393.1418115678000@Atlassian.JIRA>
References: <JIRA.12760393.1418115678000@Atlassian.JIRA>
 <JIRA.12760393.1418115678038@arcas>
Subject: [jira] [Commented] (CAMEL-8135) DeadLetterChannel moves message to
 DLQ before FailOverLoadBalancer attempts the second node
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239233#comment-14239233 ] 

metatech commented on CAMEL-8135:
---------------------------------

Also, my understanding from CAMEL-1479 is that this attribute will be removed from Camel 3.0 ? Is it still applicable ?

> DeadLetterChannel moves message to DLQ before FailOverLoadBalancer attempts the second node
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-8135
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8135
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.13.2
>         Environment: ServiceMix 5.3.0
>            Reporter: metatech
>            Assignee: Claus Ibsen
>         Attachments: myservice.xml
>
>
> When a route is defined with both a "errorHandlerRef" and a failover load balancer, the DeadLetterChannel considers the message as failed and moves it to the Dead Letter Queue, before the failover load balancer could try the second node.
> In attachment, there is a a test driver that reproduces the problem. Two HTTP backends are created : the first is down and the second is up.
> A "timer" route calls :
> 1. a route with load balancing and *without* DLQ : this works fine.  An HTTP request is sent to the first node (which is down). Afterwards another HTTP request is sent to the second node (which is up).
> 2. a route with load balancing and *with* DLQ : this does not work.  An HTTP request is sent to the first node (which is down). Afterwards, the request is moved to the DLQ, without attempting the second node.
> I suspect that the problem occurs because the error persists in the "UnitOfWork".
> The problem is reproduceable both in Camel 2.10.7 and 2.13.2.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)