[rabbitmq-discuss] Retry Message for 3 times and make it as dead

[Michael Klishin]

On 15 May 2014 at 22:02:22, Srinath Sridharan -X (srinatsr - ZENSAR TECHNOLOGIES INC at Cisco) (srinatsr at cisco.com) wrote:
> > How to keep tracke of redeliveries and message (payload) has  
> unique identifier too.

If you have only one consumer app, keeping a synchronised map around (message id => # of redeliveries) should be sufficient.

If you plan on deploy multiple instances of your app, use a data store that supports
counters (e.g. Redis).

Note that message id makes more sense in message properties or headers. This way you
won't waste cycles parsing message payload over and over. 
--  
MK  

Software Engineer, Pivotal/RabbitMQ