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 message? James.Strachan wrote: > > 2008/9/8 Demian Mrakovich <[EMAIL PROTECTED]>: >> >> 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 > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://open.iona.com > > -- View this message in context: http://www.nabble.com/Question%3A-Object-properties-on-DLQ-%28adding-exception-to-message-for-DLQ%29-tp19369459p19373787.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
