<div dir="ltr">So this would mean that I need a mechanism on my Consumer side (application B) which will do the following:<div>- rejecting the message (based on some logic) and�</div><div>- setting the requeue flag to false.</div>
<div><br></div><div style>Thanks for the insight Emile, much appreciated.</div><div style><br></div><div style>K.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 19 April 2013 12:27, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi,<br>
<div class="im"><br>
On 19/04/13 11:17, Kwstantinos Polydwrou wrote:<br>
> 4. Application B throws an NPE during the processing.<br>
</div>You don't need dead-lettering for this scenario. If Application B<br>
crashes while processing an unacknowledged message then that message<br>
will be returned to the queue and will be redelivered when Application B<br>
restarts.<br>
<br>
See the section on message acknowledgement in the second tutorial at<br>
<a href="http://www.rabbitmq.com/tutorials/tutorial-two-python.html" target="_blank">http://www.rabbitmq.com/tutorials/tutorial-two-python.html</a><br>
<br>
Dead-lettering is applicable when a message is rejected with the requeue<br>
flag set to false; or if a message expires.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
-Emile<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>