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

[Srinath Sridharan -X (srinatsr - ZENSAR TECHNOLOGIES INC at Cisco)]

Thanks for your response.
> 1. Retry unacknowledged RabbitMQ message in 10 second interval 2. 
> Retry 3 times



 * With consumers you need to manually keep track of redeliveries (this means messages should have unique identifiers)

How to keep tracke of redeliveries and message (payload) has unique identifier too.

Can you please help?


Regards ……
Srinath

-----Original Message-----
From: Michael Klishin [mailto:mklishin at gopivotal.com] 
Sent: Thursday, May 15, 2014 10:56 AM
To: Srinath Sridharan -X (srinatsr - ZENSAR TECHNOLOGIES INC at Cisco); Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Retry Message for 3 times and make it as dead



On 15 May 2014 at 21:50:50, Srinath Sridharan -X (srinatsr - ZENSAR TECHNOLOGIES INC at Cisco) (srinatsr at cisco.com) wrote:
> >
> 1. Retry unacknowledged RabbitMQ message in 10 second interval 2. 
> Retry 3 times

Are you talking about publisher confirms or message acknowledgements? Although in both cases, it's up to your applications:

 * With publisher confirms you fully control when and how many times you retry
 * With consumers you need to manually keep track of redeliveries (this means messages should have unique identifiers)

> 3. Put the message into the Dead Letter queue after 3 retries.

RabbitMQ has dead letter exchanges:
http://www.rabbitmq.com/dlx.html

which can work in concert with TTL:
http://www.rabbitmq.com/ttl.html

or you could just publish a message to a queue of your choice using the default exchange (see tutorial 1). 

> 4. Log a proper message for each action in RabbitMQ

Firehose and Tracer: http://www.rabbitmq.com/firehose.html
--
MK  

Software Engineer, Pivotal/RabbitMQ