camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: diagnosing onException problem?
Date Sat, 08 Mar 2014 07:23:47 GMT
Hi

You need to turn on backoff with
useExponentialBackOff()

And debugging see
http://camel.apache.org/how-do-i-debug-my-route.html

.. and debugging the source is a bit tougher, but see
CamelInternalProcessor which is a central class during Camel routing.

On Fri, Mar 7, 2014 at 10:35 PM, Keith Freeman <8forty@gmail.com> wrote:
> I have this code in my route:
>
>         onException(Exception.class)
>                 .handled(true)
>
>                 .maximumRedeliveries(-1)
>                 .redeliveryDelay(1L * 1000L)
>                 .backOffMultiplier(2.0D)
>                 .maximumRedeliveryDelay(60L * 1000L)
>
>                 .logRetryAttempted(true)
>                 .retryAttemptedLogLevel(LoggingLevel.WARN)
>                 .logRetryStackTrace(true)
>
>                 .logStackTrace(true)
>                 .log(LoggingLevel.ERROR,
>                         ConfiguredRouteBuilder.class.getSimpleName() +
> ": onException handler: caught Exception! ${property." +
> Exchange.EXCEPTION_CAUGHT + "}")
>
>
> But when an exception happens, the delay between retries is always 1
> second (or whatever I change the redeliveryDelay number to), there's
> never any backoff (the retry logs are always 1-second apart).  So 2
> questions:
>
> 1- why isn't the backoff multiplier having any effect?
> 2- is there a way (short of stepping through Camel source code) for me
> to diagnose something like this?
>
> (I'm on camel 2.12.1)
>
>
>
>
>



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io

Mime
View raw message