activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Demian Mrakovich <>
Subject Re: Question: Object properties on DLQ (adding exception to message for DLQ)
Date Mon, 08 Sep 2008 14:55:33 GMT

So what you are practically saying is that should I drop the built-in
retry/DLQ mechanism and implement my own? 

Calling clearProperties() on the message makes the properties writable
again, I can get the new property values on the retry, but the original
values are back when received on the DLQ, even JMSXDeliveryCount is reset to
1 again. 

I think I just don't understand how ActiveMQ handles this. The message in
the retry loop and the message received on the DLQ is obviously not the same
message (instance). The message sent to DLQ is a copy of the original

James.Strachan wrote:
> 2008/9/8 Demian Mrakovich <>:
>> Thanks for reply!
>> Not sure what you mean by create a new message. Rollback/retries are
>> handled
>> by transactions. Creating a new message from the client can't be
>> right...?
>> Can you please explain further?
> If you consume messages you can't modify them and put them back, other
> than by consuming them and sending another message.
> -- 
> James
> -------
> Open Source Integration

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message