<div dir="ltr">I am really appreciated for your enthusiastic reply, guys!</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Dec 22, 2012 at 3:54 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 21/12/12 02:02, javaLee wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
/*M*//y understanding/: Queue in rabbitmq broker will never drop the<div class="im"><br>
unacknowledged message before client ack-or-reject it,<br>
ack-or-reject-operationing on the client side do not need resend the<br>
message to rabbitmq broker, that's why client side cannot modify the<br>
message, is that true?<br>
</div></blockquote>
<br>
Correct.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I really need the requeue function, because on client side i want do<br>
some retry operation with spring-retry. if max-retry-count is exhausted<br>
& the message is still not be processing appropriately, i will not<br>
requeue it (to the original queue) any more & put it to the<br>
dead-letter-exchange.<br>
But before put it to the DLX, i really want add some error-description<br>
to this message, So another consumer that listening to the DLX can<br>
retrieve & analysis & process it according to the error-description,<br>
that's why i want modify message before reject it.<br>
</blockquote>
<br></div>
So don't use reject. Instead publish the modified message to the original queue or DLX - depending on the retry-count - and ack the original message.<br>
<br>
Regards,<br>
<br>
Matthias<br>
</blockquote></div><br></div>