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: DLQ, cause:null
Date Sat, 18 Apr 2015 05:30:33 GMT
Hi

It smells like an error message from ActiveMQ, that text is not in the
Camel codebase

davsclaus:~/workspace/camel (master)/$ git grep -i "Exceeded redelivery policy"
davsclaus:~/workspace/camel (master)/$

On Fri, Apr 17, 2015 at 5:55 PM, James Green <james.mk.green@gmail.com> wrote:
> We have a camel route consuming from ActiveMQ and occasionally get a DLQ
> entry without anything logged through our deadLetterChannel.
>
> The only thing we have to go on is a dlqFailureCause header which says:
>
> java.lang.Throwable: Exceeded redelivery policy limit:RedeliveryPolicy
> {destination = null, collisionAvoidanceFactor = 0.15, maximumRedeliveries =
> 6, maximumRedeliveryDelay = -1, initialRedeliveryDelay = 1000,
> useCollisionAvoidance = false, useExponentialBackOff = false,
> backOffMultiplier = 5.0, redeliveryDelay = 1000}, cause:null
>
> The suggestion internally is that because the deadLetterChannel goes to a
> route that logs the exception on the Exchange, yet we have nothing logged,
> the camel route was in fact not involved thus perhaps it's an ActiveMQ
> problem.
>
> ActiveMQ, for it's part, logged nothing either.
>
> Any suggestions at all?
>
> Thanks,
>
> James



-- 
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
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Mime
View raw message