Timeout::Error: execution expired when opening queue?

[Christoph Blank]

Hi there,

I've got a rails application that I am switching over to ruby bunny.
I've got the following initializer: https://gist.github.com/solars/e4b99ef4a1483bb0a7d5

I then start rails with rails console and executed the code in the second file above to push to a queue.
I keep getting (on q = ...):

Timeout::Error: execution expired
from /home/solars/.rvm/rubies/ruby-1.9.3-p545/lib/ruby/1.9.1/thread.rb:189:in `sleep'

Can anyone tell me how to fix this?

Thank you,
Christoph

[Michael Klishin]

On 2 July 2015 at 14:19:41, Christoph Blank (christo...@seekda.com) wrote:
> Timeout::Error: execution expired
> from /home/solars/.rvm/rubies/ruby-1.9.3-p545/lib/ruby/1.9.1/thread.rb:189:in
> `sleep'

What's in RabbitMQ log files? 
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Michael Klishin]

On 2 July 2015 at 14:21:32, Michael Klishin (mic...@rabbitmq.com) wrote:
> I then start rails with rails console and executed the code in
> the second file above to push to a queue.
> I keep getting (on q = ...):

While I'm not really familiar with how irb is implemented, I've seen first
hand that it affects thread scheduling.

For example, a message consumed by a Bunny consumer but you won't observe
the effect of this unless you hit Enter multiple times in the REPL to
make its (keyboard) event loop thread yield. 

[Christoph Blank]

I think you are right - I've moved the test to an rspec spec, and it worked there everytime..

Thanks a lot!

Christoph