From: Mohamed Hafez <mohamed.m.m.hafez@...>
Date: 2016-05-30T09:18:36-07:00
Subject: [ruby-core:75774] Errno::EAGAIN thrown by	OpenSSL::SSL::SSLSocket#connect_nonblock

--===============0618619631==
Content-Type: multipart/alternative; boundary=001a113f9994d37c6b0534119bf6

--001a113f9994d37c6b0534119bf6
Content-Type: text/plain; charset=UTF-8

Hi all, every now and then in my production server, I'm
getting Errno::EAGAIN errors thrown by by
OpenSSL::SSL::SSLSocket#connect_nonblock from at
https://github.com/ruby/ruby/blob/trunk/lib/net/http.rb#L938

I'm using JRuby, so initially I assumed it was just a JRuby implementation
bug and that MRI's  OpenSSL::SSL::SSLSocket#connect_nonblock must
handle Errno::EAGAIN internally, but now that I think about it, the only
way to handle Errno::EAGAIN is to wait for a bit and then retry, and
connect_nonblock isn't supposed to block so how would it do that....

Since this only happens once in a while in production, I don't actually
have a way of seeing if MRI Ruby will also throw this error, but I can't
see how it wouldn't if connect_nonblock can't block for a while before
retrying, but let me know if I'm wrong. If I am correct, could I submit a
pull request to catch Errno::EAGAIN at
https://github.com/ruby/ruby/blob/trunk/lib/net/http.rb#L938 and then retry?

Thanks!
Mohamed

--001a113f9994d37c6b0534119bf6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all, every now and then in my production server, I&#39;=
m getting=C2=A0Errno::EAGAIN errors thrown by by OpenSSL::SSL::SSLSocket#co=
nnect_nonblock=C2=A0from at=C2=A0<a href=3D"https://github.com/ruby/ruby/bl=
ob/trunk/lib/net/http.rb#L938">https://github.com/ruby/ruby/blob/trunk/lib/=
net/http.rb#L938</a><div><br></div><div>I&#39;m using JRuby, so initially I=
 assumed it was just a JRuby implementation bug and that MRI&#39;s =C2=A0Op=
enSSL::SSL::SSLSocket#connect_nonblock must handle=C2=A0Errno::EAGAIN inter=
nally, but now that I think about it, the only way to handle Errno::EAGAIN =
is to wait for a bit and then retry, and connect_nonblock isn&#39;t suppose=
d to block so how would it do that....</div><div><br></div><div>Since this =
only happens once in a while in production, I don&#39;t actually have a way=
 of seeing if MRI Ruby will also throw this error, but I can&#39;t see how =
it wouldn&#39;t if connect_nonblock can&#39;t block for a while before retr=
ying, but let me know if I&#39;m wrong. If I am correct, could I submit a p=
ull request to catch=C2=A0Errno::EAGAIN at <a href=3D"https://github.com/ru=
by/ruby/blob/trunk/lib/net/http.rb#L938">https://github.com/ruby/ruby/blob/=
trunk/lib/net/http.rb#L938</a> and then retry?</div><div><br></div><div>Tha=
nks!</div><div>Mohamed</div></div>

--001a113f9994d37c6b0534119bf6--

--===============0618619631==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

--===============0618619631==--