Matthias,<div><br><br><div class="gmail_quote">On Mon, May 24, 2010 at 12:54 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,<div class="im"><br>
<br>
allan bailey wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Apparently the AMQP protocol does not<br>
send an exception to an active client connection until it reconnects or re-requests access.<br>
</blockquote>
<br></div>
When the memory alarm is raised, RabbitMQ sends a channel.flow on all channels. There are no delays other than the usual processing and networking delays.<br>
<br>
Also, access.request is a no-op in RabbitMQ and has been removed from the AMQP spec in 0-9-1. There is on need for clients to ever invoke it.<br><font color="#888888">
<br>
<br></font></blockquote><div><br></div><div>So should I just redeclare my exchange, would that be a sufficient no-op?</div><div><br></div><div> I tested it just now and it works to trigger the alert.</div><div><br></div>
<div>-allan</div><div><br></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></div>