That's true. It seems that all that happens is that the messages (which are persistent in my case) are maintained in the queue and do not get removed until the acks are received. However, all the messages are still sent. I assume they would be retransmitted at some point. It's quite interesting :).<br>
<br>Ed<br><br><div class="gmail_quote">On Thu, May 8, 2008 at 12:22 AM, Matthias Radestock <<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Edwin Fine wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
***** Actually, I believe I have turned off the no_ack flag and am actively sending acks when appropriate. [...]<div class="Ih2E3d"><br>
However, I must have done something wrong because RMQ continues to send even if I haven't acked.<br>
</div></blockquote>
<br>
You haven't done anything wrong. The no_ack flag controls whether the server expects to see acks from the client, or just auto-acks the messages itself. The flag does not affect the flow of messages.<br><font color="#888888">
<br>
<br>
Matthias.<br>
<br>
</font></blockquote></div><br>