Hi, we keep seeing the following exception in our logs:
E, [2017-01-16T12:08:06.934348 #15759] ERROR -- : Resource temporarily unavailable - read would block (IO::EAGAINWaitReadable)
<internal:prelude>:76:in `__read_nonblock'
<internal:prelude>:76:in `read_nonblock'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/cruby/socket.rb:42:in `block in read_fully'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/cruby/socket.rb:41:in `loop'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/cruby/socket.rb:41:in `read_fully'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/transport.rb:214:in `read_fully'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/transport.rb:236:in `read_next_frame'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/reader_loop.rb:68:in `run_once'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/reader_loop.rb:35:in `block in run_loop'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/reader_loop.rb:32:in `loop'
/var/www/apps/platform-api-etl/shared/bundle/ruby/2.3.0/bundler/gems/bunny-8f0fc31cfab6/lib/bunny/reader_loop.rb:32:in `run_loop'
Based on this post I assumed that I just needed to add IO::EAGAINWaitReadable to the list of READ_RETRY_EXCEPTION_CLASSES. I tried that in a fork of this gem, but it had no effect.
Of course, they have no documentation but the idea is
probably the same as with the classic versions.
Fixes#456.
michaelklishin
changed the title
IO::EAGAINWaitReadable
ready_full does not retry on IO::EAGAINWaitReadable (new in Ruby 2.1+)
Jan 16, 2017
michaelklishin
changed the title
ready_full does not retry on IO::EAGAINWaitReadable (new in Ruby 2.1+)
read_fully does not retry on IO::EAGAINWaitReadable (new in Ruby 2.1+)
Jan 16, 2017
Hi, we keep seeing the following exception in our logs:
Based on this post I assumed that I just needed to add
IO::EAGAINWaitReadable
to the list ofREAD_RETRY_EXCEPTION_CLASSES
. I tried that in a fork of this gem, but it had no effect.We are running Ruby 2.3.
Is this expected behavior or does it indicate a problem?
The text was updated successfully, but these errors were encountered: