Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.218.178 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=xLPncd+Zs3Mutq0OS8L5ugz0syOGamtZ4HpiQXJm7WJGcTuZ8Yvh5u/tSToPLXEF3E
         L72RihWMoMZyKfnm+Cv5z4y05U2maxggQwitrnykRNnz5c5+/NeJPgc6oqpH68YnOq4A
         VG6LzzFWECywl7PhYLDRAbEGEaUFFG5clrXO4=
MIME-Version: 1.0
In-Reply-To: <22916317.post@talk.nabble.com>
References: <22916317.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 7 Apr 2009 08:57:17 +0200
Message-ID: <5380c69c0904062357y71be25fdxb092f380168a392c@mail.gmail.com>
Subject: Re: Capturing Exception Causing ActiveMQ Rollback
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 6, 2009 at 10:12 PM, greenbean <Kevin.Urciolo@ngc.com> wrote:
>
> I would like to capture the exception that caused an ActiveMQ rollback wh=
en
> using Apache Camel. =A0I would also like to associate it with the message=
 (by
> message id?) so that I can find the exception again when I am processing =
the
> message in an ActiveMQ DLQ.
>
> What is the best way to accomplish this with Apache Camel? =A0Currently I=
 am
> using bean components that are abstracted from JMS. =A0Without Camel I wo=
uld
> catch the exception in onMessage and write it out along with the message =
id
> found in the Message object. =A0I don't really have this option when deal=
ing
> with bean components.
>
> Is there a way to place an interceptor in the ActiveMQ or transaction
> components to let me capture the exception and JMS message id on rollback=
?
Hi

You can use the try .. catch style as the routing is transacted then
it should be marked for rollback, the (*) rehtrow might not be needed,
but if having it it more clearly state the intention like we will do
in regular java code.

from(jms) -> policy(required) -> tryBlock -> do your routing here ->
handle(Exception.class) -> log exception and message id -> (*) rethrow
->  end

Note:
In Camel 2.0 we have a new rollback DSL keyword you can use as well.
And the onException also works with the transacted error handler in Camel 2=
.0.


>
> Thanks.
> --
> View this message in context: http://www.nabble.com/Capturing-Exception-C=
ausing-ActiveMQ-Rollback-tp22916317p22916317.html
> Sent from the Camel - Users (activemq) mailing list archive at Nabble.com=
.
>
>


--=20
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration