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.220.177 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=JKXUfjTe2PCM6H3E29cuTZqu3p9+CJXO41Ko7fSiyOBNWOPtMZg8ScJVulqrE50ks3
         FRZZSiPqj4n+5W5XLQ6y8vbDl1op+jz5XOR2ytTlraUvLT+h57DvAfr6nrLbqMoFtgLa
         Bhq4Qokl5Moft7Qhg2I9hvksTc7zrhVgZC6G0=
MIME-Version: 1.0
In-Reply-To: <23743717.post@talk.nabble.com>
References: <23743717.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 27 May 2009 16:50:43 +0200
Message-ID: <5380c69c0905270750t8611a37g4ba4eca129118180@mail.gmail.com>
Subject: Re: Exception, ErrorHandler and redelivery
To: users@camel.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi

Yeah error handling and redelivery is hard.

1)
onRedelivery is *only* executed when Camel performs a redelivery
attempt. That is it retries processing some exchange that failed last
time.

2)
onException will by default not do any redelivery attempts, unless you
set a maximumRedelivers option >=3D 1.

So in your first attempt Camel will by the onException catch the
RuntimeException and *not do any redeliveries* as maximumRedelivers is
by default =3D 0 for onException.

So when you change the maximumRedeliveries =3D 1 then the onRedelivery
processor kicks in as expected.
onRedelivery is meant to allow you to do a bit of custom message
adjustment before Camel retries. And yes it can also be used for
logging.


On Wed, May 27, 2009 at 4:32 PM, mta38 <mtaraud.ext@orange-ftgroup.com> wro=
te:
>
> Hi all,
>
> I play with Exception, ErrorHandler and redelivery (Camel 2.0-M1) and the=
re
> are some things =A0that I can't understand :confused:.
>
> snippet code
>
> <bean id=3D"globalDeadLetterChannel"
> class=3D"org.apache.camel.builder.DeadLetterChannelBuilder">
> =A0 =A0 =A0 =A0 <property name=3D"defaultDeadLetterEndpointUri"
> value=3D"direct:response"/>
> =A0 =A0<property name=3D"onRedelivery" ref=3D"routeRedelivery"/>
> =A0 =A0 =A0 =A0 =A0<property name=3D"redeliveryPolicy">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<bean id=3D"redeliveryPolicyConfig"
> class=3D"org.apache.camel.processor.RedeliveryPolicy">
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <property name=3D"maximum=
Redeliveries" value=3D"1"/>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</bean>
> =A0 =A0 =A0 =A0 </property>
> =A0 =A0 =A0 =A0 </bean>
>
> <camelContext =A0id=3D"camelContext" =A0errorHandlerRef=3D"globalDeadLett=
erChannel"
> xmlns=3D"http://camel.apache.org/schema/spring">
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<onException >
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<exception>java.lang.Runti=
meException</exception>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<handled>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<constant>=
true</constant>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</handled>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<to uri=3D"direct:response=
" />
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0</onException>
>
> =85 other routes =85
>
> </camelContext>
>
> routeRedelivery bean is a processor which make some trace =A0in a log fil=
e.
>
> When I raise a runtimeException, the process method of routeRedelivery be=
an
> is not called. I can't understand why, since onRedelivery property is
> defined for my global dead letter channel.
>
> If I modify onException element like following:
>
>
> <onException onRedeliveryRef=3D"routeRedelivery">
> <exception>java.lang.RuntimeException</exception>
> =A0 =A0 =A0 =A0<redeliveryPolicy maximumRedeliveries=3D"1"/>
> =A0 =A0 =A0 =A0<handled>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<constant>true</constant>
> =A0 =A0 =A0 =A0</handled>
> =A0 =A0 =A0 =A0<to uri=3D"direct:response" />
> </onException>
>
>
> And I raised a RuntimeException, I have some trace in my log file that
> proves that process method of routeRedelivery bean is called.
>
> Is someone can explain me why onRedelivery processor is not called when i=
t's
> defined in global scope will be appreciated.
> Best regards,
> Mta38
>
> --
> View this message in context: http://www.nabble.com/Exception%2C-ErrorHan=
dler-and-redelivery-tp23743717p23743717.html
> Sent from the Camel - Users 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