[rabbitmq-discuss] Resource alarms in 3.1 seems to block operations other than basic.publish

[Michael Klishin]

I'm observing something odd since upgrading to 3.1.

I'm adding various stress tests for Bunny and hit RAM alarms every
so often. After that happens, starting new consumers takes so long
that it times out in the client. Also, I've noticed in the management UI
that existing consumers do not drain queues.

Sometimes Rabbit stops responding altogether.

Steps to reproduce:

 * Start a "hello, world"-like consumer and producer
 * Make the producer publish large (tens of MBs) messages as fast as it can
 * See an alarm message in the log
 * Shut down the publisher

At this point, consumers receive no deliveries.

 * Shut down the consumer
 * Start the consumer again with log level = debug

The consumer seems completely blocked, receiving no methods from RabbitMQ.

 * Purge the queue

Now consumer can start, open a connection and register consumers
successfully.
-- 
MK

http://github.com/michaelklishin
http://twitter.com/michaelklishin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130503/155fbd58/attachment.htm>