<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 13 May 2013, at 18:21, Michael Klishin wrote:</div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/5/13 Tim Watson <span dir="ltr"><<a href="mailto:tim@rabbitmq.com" target="_blank">tim@rabbitmq.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I didn't try that, but it wouldn't make any difference if that alarm was still set, since the producer would get blocked immediately would it not?</blockquote></div><br>I first clear the queue, then restart the producer, so no.<br></div></div></blockquote><div><br></div><div>Hmn, I can't get that to break, because I can't get the queue to be non-empty in the first place. Here's what I'm doing, perhaps you can point out the step I'm missing.</div><div><br></div><div>1. start the broker</div><div>2. start the producer</div><div>3. start the consumer</div><div>4. set the watermark very low using rabbitmqctl, e.g., 0.001</div><div>5. see the alarm in the logs</div><div>6. stop the producer</div><div><br></div><div>** at this point, the queue is always empty</div><div><br></div><div>7. stop the consumer</div><div>8. start the consumer</div><div><br></div><div>** but at this point, the exercise is moot, because the queue is empty so 'blocking' is the expected state. Sorry I didn't check on this with you sooner - I didn't realise I needed to look at that when I got started as I wasn't clear on the implication of "blocking" as the consumer state. The consumer stays in this state of course, since there are no messages in the queue.</div><div><br></div><div>So what am I doing wrong here?</div><div><br></div><div>Cheers,</div><div>Tim</div></div></body></html>