[rabbitmq-discuss] Resource alarms in 3.1 seems to block operations other than basic.publish
tim at rabbitmq.com
Mon May 13 18:45:33 BST 2013
On 13 May 2013, at 18:21, Michael Klishin wrote:
> 2013/5/13 Tim Watson <tim at rabbitmq.com>
> 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?
> I first clear the queue, then restart the producer, so no.
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.
1. start the broker
2. start the producer
3. start the consumer
4. set the watermark very low using rabbitmqctl, e.g., 0.001
5. see the alarm in the logs
6. stop the producer
** at this point, the queue is always empty
7. stop the consumer
8. start the consumer
** 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.
So what am I doing wrong here?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss