The message is always refelivered from the server.
This was done so other consumers would have a chance to receive it as well. (Say if there is something wrong with that particular consumer) This would require some hashnap at the client. Functionality you can implement yourself based on the Id and what you want to store. I would use some Caching strategy. You can also use interceptors on client. Notice I'm talking about the core client here. You have to also account about other protocols. On Wed, May 24, 2017 at 4:50 AM vishal3007 <vishal3...@gmail.com> wrote: > Thanks for the detailed response...Just a suggestion- > I believe when consumer consumes the message from a queue it gets the same > Message object everytime(in case of re-delivery)...Can't we add a property > in the message which can be set by the consumers. Consumer should only be > allowed to set this property in the message rest can be readonly.? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Artemis-failure-cause-of-DLQ-messages-tp4726423p4726468.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- Clebert Suconic
