Hello JRubians,
bundle install tosses a OpenSSL::SSL::SSLError: Socket closed
I am fishing around to see if anyone else has seen something similar.
When my CI server is under load, which is fairly regularly on the small
EC2 server, I get an “OpenSSL::SSL::SSLError: Socket closed” when
“bundle install --deployment” is run. Gist of the Jenkins output[1]. The
output for this was for installing a single gem, railroady. It happens
fairly regularly, but when the load drops on the box, the install will
work again.
[1] Bundle install fails for JRuby 1.7.3 · GitHub
thanks,
Michael
Hi Michel,
I’m getting the same issue reliably(!) on Mac OS X (10.8.2) running
oracle
java 1.7.0_15 and jruby 1.7.3 or 1.7.2 (I haven’t tried older versions
of
jruby, nor have I tried under jdk 6).
The same configuration (ie same versions of java and jruby) work fine
under
ubuntu.
I assume you’re running under linux, but are you also using oracle java
7
update 15?
Thanks,
Michael
OK, so I was able to solve (maybe workaround) my particular problem, and
it
may helpful for you or others.
I changed the rubygems “source” line in the Gemfile
from
source ‘https://rubygems.org’
to
source ‘https://bundler.rubygems.org’
It seems that rubygems.org was redirecting to bundler.rubygems.org (302
result code) and that seemed to be causing grief somewhere in the
handling
of the response.
I’m not sure if this will be a long-term solution, since rubygems may
decide to change the server handing that API, but as a workaround it’s
working for now.
Regards,
Michael