Matthias,<br><br><div class="gmail_quote">On Mon, May 24, 2010 at 10:47 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">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;">
Allan,<br>
<br>
allan bailey wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Mon, May 24, 2010 at 12:54 PM, Matthias Radestock <<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a> <mailto:<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>>> wrote:<br>
When the memory alarm is raised, RabbitMQ sends a channel.flow on<br>
all channels. There are no delays other than the usual processing<br>
and networking delays.<br>
<br></div><div class="im">
So should I just redeclare my exchange, would that be a sufficient no-op?<br>
<br>
I tested it just now and it works to trigger the alert.<br>
</div></blockquote>
<br>
You shouldn't have to do send any other command - if the client library is implemented correctly.<br><font color="#888888">
<br>
<br></font></blockquote><div><br></div><div>Are you suggesting that basic_publish should return something? From my brief reading of the protocol it doesn't return anything.</div><div><br></div><div>In my code I'm in a tight look just sending messages via basic_publish. At no point does basic_publish notice the channel.flow state change.</div>
<div><br></div><div>I'll take a look at the java and/or php clients and see how they handle this.</div><div><br></div><div>-allan</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888">
Matthias.<br>
</font></blockquote></div><br>