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 may be of limited value. if you want to depend on the redelivery
counter you may want to peek at the persistjmsredelivery option.

On Tue 3 Nov 2015 3:45 PM Martin Lichtin <lich...@yahoo.com.invalid> wrote:

> 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
>

Reply via email to