Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.220.216 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=GmgQxa/13SPe+9D0kV+YDjePMPARUYlEiQKE0Bjg9wLfDuqQOBJOnbAccqBUjkXOWX
         LFnbFs4ONuvHdY6px77oaK2mFctvywhaLYaoRUAEF2KnAAbev68kSfOmwj3p9FZRxxv3
         uAHox3SX7RNfVScO/nLkYkAV2T/FKEa8f6IYs=
MIME-Version: 1.0
In-Reply-To: 
 <AB7C019E505B9F4D95F6B6303A215C7C146B2043@CIWMEXZSA0E.ex.ordersx.org>
References: 
 <AB7C019E505B9F4D95F6B6303A215C7C146B2043@CIWMEXZSA0E.ex.ordersx.org>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 26 Aug 2009 13:52:53 +0200
Message-ID: <5380c69c0908260452x3630295eqfaba2f784f521deb@mail.gmail.com>
Subject: Re: Dead Letter Queue, Exception Preservation Question.
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Exception caused =3D Exchange.getProperty(Exchange.EXCEPTION_CAUGHT,
Exception.class);


On Wed, Aug 26, 2009 at 1:46 PM, Bach
Christian<Christian.Bach@six-group.com> wrote:
> Heya
>
> How do I make Camel preserve the caught exception when putting a failed
> exchange into a dead letter queue ? The below Camel code on execution,
> clears the exception out. Is there a way to have exchanges in a dead
> letter queue which have the original exception still set, so we can
> report the particular exception which caused the exchange to fail, once
> we take it off the queue ?
>
> /**
> =A0 =A0 * All redelivery attempts failed so move the exchange to the dead
> letter queue
> =A0 =A0 */
> =A0 =A0protected void deliverToFailureProcessor(final Processor processor=
,
> final Exchange exchange,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 final RedeliveryData data)
> {
> =A0 =A0 =A0 =A0// we did not success with the redelivery so now we let th=
e
> failure processor handle it
> =A0 =A0 =A0 =A0// clear exception as we let the failure processor handle =
it
> =A0 =A0 =A0 =A0exchange.setException(null);
>
> =A0 =A0 =A0 =A0if (data.handledPredicate !=3D null &&
> data.handledPredicate.matches(exchange)) {
> =A0 =A0 =A0 =A0 =A0 =A0// its handled then remove traces of redelivery at=
tempted
> =A0 =A0 =A0 =A0 =A0 =A0exchange.getIn().removeHeader(Exchange.REDELIVERED=
);
> =A0 =A0 =A0 =A0 =A0 =A0exchange.getIn().removeHeader(Exchange.REDELIVERY_=
COUNTER);
> =A0 =A0 =A0 =A0} else {
> =A0 =A0 =A0 =A0 =A0 =A0// must decrement the redelivery counter as we did=
n't
> process the redelivery but is
> =A0 =A0 =A0 =A0 =A0 =A0// handling by the failure handler. So we must -1 =
to not let
> the counter be out-of-sync
> =A0 =A0 =A0 =A0 =A0 =A0decrementRedeliveryCounter(exchange);
> =A0 =A0 =A0 =A0}
>
> Any help appreciated, thx, and regards, Christian.
>
> This message is for the named person's use only. It may contain confident=
ial, proprietary or legally privileged information. If you receive this mes=
sage in error, please notify the sender urgently and then immediately delet=
e the message and any copies of it from your system. Please also immediatel=
y destroy any hardcopies of the message.
> The sender's company reserves the right to monitor all e-mail communicati=
ons through their networks.
>


--=20
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus