-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeout::Error Timeout::Error #502
Comments
Please post question to the mailing list in the future. An operation that expects a response times out. This is not an indication of an issue in the client but it happens that you are running a version that does not include #462 (and I only know this from the stack trace, please do report versions of the libraries used when seeking help). |
See server logs for any possible alarms and that both the app's and node's TCP buffers aren't too small. |
I updated to 2.6.5 and the error continues. |
@blanchma the stack trace says a |
I still have this issue with 2.7.0 and still clueless about the issue:
My connection class is like this:
Any time I want to publish or suscribe, I use AmqpConnection.create_channel but I get this Timeout::Error with too much frecuency. |
The code does no synchronization and does not demonstrate how channels or connections are used. Take a traffic capture with Wireshark and see what's actually sent on the wire. |
I'm having an issue in one of the environments in which I run Bunny. It's weird because it's only happen in one env. The error is a Timeout. I don't share the connection between multiple threads but I have a Singleton to only build one session to prevent every time I sent a message a create a new session. If I build a session per message, the timeout dissapears. I'll like to understand what is going on in the line 33:
Stacktrace
/opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/concurrent/continuation_queue.rb:33:in `block in poll' /opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/concurrent/continuation_queue.rb:30:in `synchronize' /opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/concurrent/continuation_queue.rb:30:in `poll' /opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/session.rb:1261:in `wait_on_continuations' /opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/session.rb:503:in `block in open_channel' /usr/local/rvm/rubies/ruby-2.3.1/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize' /opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/session.rb:496:in `open_channel' /opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/channel.rb:223:in `open' /opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/session.rb:345:in `block in create_channel' /usr/local/rvm/rubies/ruby-2.3.1/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize' /opt/rubyapp/concourse/releases/20170505184556/vendor/bundle/ruby/2.3.0/gems/bunny-2.6.2/lib/bunny/session.rb:340:in `create_channel'
The text was updated successfully, but these errors were encountered: