it has additional property:
>>>>
>>>> dlqDeliveryFailureCause=java.lang.Throwable: Exceeded redelivery policy
>>>> limit:RedeliveryPolicy {destination = null, collisionAvoidanceFactor =
>>>> 0.15, maximumRedeliveries = 0, maximumRedeliveryDelay = -1,
&
e);
>>> }
>>> }
>>>
>>> should also set md.setRollbackCause(e) in the else clause?
>>>
>>> - Martin
>>>
>>> --
>>> *From:* Martin Lichti
pache.org>
*Sent:* Wednesday, November 4, 2015 12:32 PM
*Subject:* Re: What happens with JMSRedelivered when server moves message
to DLQ
I'm not actually talking about the counter, but the Boolean flag
'JMSRedelivered'.
Anyways, you're right that it should work when s
}
>
> should also set md.setRollbackCause(e) in the else clause?
>
> - Martin
>
> --
> *From:* Martin Lichtin
> *To:* Gary Tully ; ActiveMQ Users <
> users@activemq.apache.org>
> *Sent:* Wednesday, November 4, 2015 12:32 PM
>
>
> *Sub
:null" would instead be shwoing the Exception
that the application threw.
- Martin
>
> From: Gary Tully
> To: Martin Lichtin ; ActiveMQ Users
>
> Sent: Wednesday, November 4, 2015 11:52 AM
> Subject: Re: What happens with JMSRedelivered when
n
that the application threw.
- Martin
>
> From: Gary Tully
> To: Martin Lichtin ; ActiveMQ Users
>
> Sent: Wednesday, November 4, 2015 11:52 AM
> Subject: Re: What happens with JMSRedelivered when server moves message to DLQ
>
>
> t
that is intended. the dlq enqueue is a new message. the poison cause
property will have some good information but it would make sense to add a
property that captures the value of that counter. the only issue is that
the value is typically interpreted client side and remains 1 on the broker
so it ma
I see the JMSRedelivered flag goes back to 'false' when # of redeliveries is
exceeded
and ActiveMQ server moving the message into the DLQ.
Is this done on purpose? I'd rather expect the flag stay 'true', as this state
should be preserved.
- Martin
