Hi Joe,
Are you acknowledging messages automatically or in your code, are you
using synchronous receipt etc?
The cause here is really that the message has actually failed 4 times -
You need to work out why the message is not being acknowledged. This is
usually a client rejecting the message (in which case you should log it).
Andy.
The initialRedeliveryDelay seems really high, is that intended?
On 05/01/2015 11:33, joeleclems wrote:
When the message is arriving in the "error queue" (named "ActiveMQ.DLQ"), the
message sent contains this exception :
/
*dlqDeliveryFailureCause : *
java.lang.Throwable: Exceeded redelivery policy limit:RedeliveryPolicy
{destination = null, collisionAvoidanceFactor = 0.15, maximumRedeliveries =
4, maximumRedeliveryDelay = -1, initialRedeliveryDelay = 10800000,
useCollisionAvoidance = false, useExponentialBackOff = true,
backOffMultiplier = 2.0, redeliveryDelay = 1000}, cause:null /
it's strange... all properties seems to be set in the
RedeliveryPolicy(maximumRedeliveries = 4, initialRedeliveryDelay = 10800000,
redeliveryBackOffMultiplier = 2, redeliveryUseExponentialBackOff = true). So
what is causing the "Exceeded redelivery policy limit" ?
thanks in advance
--
View this message in context:
http://tomee-openejb.979440.n4.nabble.com/TomEEplus-Activemq-RedeliveryDelay-not-working-tp4673241p4673324.html
Sent from the TomEE Users mailing list archive at Nabble.com.
--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
