You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by nomit babraa <h....@sheffield.ac.uk> on 2020/03/02 22:14:45 UTC

dlqDeliveryFailureCause cause is null

Hi

When I use a transacted JMS client, camel propagates non handled
exceptions back to the Broker. After max redeliveries the message is
sent to the AMQ DLQ with a dlqDeliveryFailureCause header that says:

java.lang.Throwable: Exceeded redelivery policy limit:RedeliveryPolicy
{destination = null, collisionAvoidanceFactor = 0.15,
maximumRedeliveries = 3, maximumRedeliveryDelay = -1,
initialRedeliveryDelay = 2000, useCollisionAvoidance = false,
useExponentialBackOff = true, backOffMultiplier = 2.0, redeliveryDelay
= 1000}, cause:null

I was wondering why the cause is null?

What is responsible for setting the cause?

The component raising the exception shows an error in the logs but it
would be great to be able to see this error on the DLQ message....

Thanks again for all the amazing current help I'm getting from this list:)

n