[rabbitmq-discuss] Resource alarms in 3.1 seems to block operations other than basic.publish
tim at rabbitmq.com
Mon May 13 16:59:00 BST 2013
A couple of quick questions about this...
1. are you sure the queue is not empty by the time the consumer is restarted?
2. do you receive no methods at all in the consumer, not even connection negotiation?
I can't replicate this viz (1) for me the queue is always empty by the time the consumer is stopped and restarted and (2) I see the connection and basic.consume get going before the consumer gets stuck and it is in 'blocking' mode, which given that the queue is empty and the alarm still set, is apparently ok.
On 3 May 2013, at 10:45, Michael Klishin wrote:
> 2013/5/3 Tim Watson <tim at rabbitmq.com>
> Have you got a reproducible (ish) test that I can run on a linux box? If so, I'll poke around and make sure it's not showing up there too.
> You'll need Ruby and RubyGems available.
> Put all 3 files in a directory, then do
> * [sudo] gem install bundler
> * bundle install
> * run bundle exec ruby ./consumer.rb and bundle exec ruby ./producer.rb in two tabs
> You can tweak message rates and size in publisher.rb. If you want to see methods
> received from rabbit, run the consumer with BUNNY_LOG_LEVEL=debug.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss