Return-Path: 
 <users-return-51512-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 293DF17799
	for <apmail-camel-users-archive@www.apache.org>;
 Thu, 16 Oct 2014 13:30:48 +0000 (UTC)
Received: (qmail 89301 invoked by uid 500); 16 Oct 2014 13:30:47 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 89252 invoked by uid 500); 16 Oct 2014 13:30:47 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 89241 invoked by uid 99); 16 Oct 2014 13:30:47 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Oct 2014 13:30:47 +0000
X-ASF-Spam-Status: No, hits=2.3 required=5.0
	tests=SPF_SOFTFAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 nabble@detroitsci.com does not designate 216.139.236.26 as permitted sender)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Oct 2014 13:30:42 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <nabble@detroitsci.com>)
	id 1Xel8I-00019k-4s
	for users@camel.apache.org; Thu, 16 Oct 2014 06:30:22 -0700
Date: Thu, 16 Oct 2014 06:30:22 -0700 (PDT)
From: nathanwray <nabble@detroitsci.com>
To: users@camel.apache.org
Message-ID: <1413466222143-5757629.post@n5.nabble.com>
In-Reply-To: <1413462902278-5757627.post@n5.nabble.com>
References: <1413401800386-5757602.post@n5.nabble.com>
 <CAAxZHdcj58s=KQKu2gEpBL98bKiZj10oO5V54G1u-dWOSDJDqQ@mail.gmail.com>
 <1413460906885-5757626.post@n5.nabble.com>
 <1413462902278-5757627.post@n5.nabble.com>
Subject: Re: onException and doTry
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

A little further digging.  I added some debugging output to
incrementRedeliveryCounter and found the CamelRedeliveryCounter header is
missing on the redelivery attempt, I see the following:

2014-10-16 09:01:48,976 [CamelJettyClient(0x106898e3)-88] DEBUG
camel.processor.RedeliveryErrorHandler in incrementRedeliveryCounter
2014-10-16 09:01:48,976 [CamelJettyClient(0x106898e3)-88] DEBUG
camel.processor.RedeliveryErrorHandler !!! redelivery counter header was
NULL
2014-10-16 09:01:48,977 [CamelJettyClient(0x106898e3)-88] DEBUG
camel.processor.RedeliveryPolicy in shouldRedeliver, redeliveryCounter = 1
2014-10-16 09:01:48,977 [CamelJettyClient(0x106898e3)-88] DEBUG
camel.processor.RedeliveryPolicy maxRedeliveries is 2, returning true

inside route2, I had a statement that removed the Camel headers before
calling a remote web service (as recommended) so that Jetty doesn't get
tripped up by the old URI, URL settings:

			<removeHeaders pattern="Camel*"/>
			<to uri="jetty:{{vendor.uri}}?httpClient.timeout=100"/>

Apparently this destroys the redelivery count, removing it corrected the
issue.  I would consider this a defect that an inner route (with
useOriginalMessage=true) can destroy the redelivery count.

I changed it to:
			<removeHeaders pattern="Camel*" excludePattern="CamelRedeliveryCounter"/>

And the issue went away, it now redelivers twice and then fails as designed.





--
View this message in context: http://camel.465427.n5.nabble.com/onException-and-doTry-tp5757602p5757629.html
Sent from the Camel - Users mailing list archive at Nabble.com.