Hi, I will take a look on the first thread email tomorrow morning.
Sorry for the delay. Regards JB > Le 27 avr. 2020 à 17:00, nomit babraa <h.bab...@sheffield.ac.uk> a écrit : > > Hi > > Wondering if anyone can help with this please? > > We are on AMQ version 5.15.0 and I found this > https://issues.apache.org/jira/browse/AMQ-6042, so I'm assuming that > is not an issue for us? > https://github.com/apache/activemq/blob/activemq-5.15.x/activemq-client/src/main/java/org/apache/activemq/ActiveMQMessageConsumer.java#L1409 > looks to have the fix. > > However this may not be relevant here, as I'm using a Camel to consume > the message? > There seems to both a JMS and ActiveMQ Component listed at > https://camel.apache.org/components/latest/index.html > > To be fair I'm nor sure which I'm using. Does only one populate this cause? > > Cheers > > n > > On Sun, 26 Apr 2020 at 09:23, nomit babraa <h.bab...@sheffield.ac.uk> wrote: >> >> Hi >> >> I'm using the Camel Transactional Client EIP with *all* delivery >> configured in AMQ. >> >> 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 configured DLQ, as expected. >> >> I've noticed that my DLQ messages have a dlqDeliveryFailureCause header. >> >> And this header has a "cause" item which is null for me: >> >> "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: >> >> 1) Should this "cause" be null? Is this an error in my setup? >> 2) What mechanism sets the cause to not null? >> 3) Ultimately, am I missing something here where an exception in my >> camel route can or should be written to this "cause" value? >> >> Thanks for any advice >> >> n
