openssl issue with rails and installed default gems #1549

Closed
mkristian opened this Issue Mar 6, 2014 · 4 comments

Projects

None yet

3 participants

@mkristian
Member

when I install the default gems:
krypt, jruby-openssl, bouncy-castle-java
tell bundler via the Gemfile to "use" them, see Gemfile from gist below. this will lead with

Bundler.require
require 'openssl'

to
NameError: uninitialized constant OpenSSL::Digest::OPENSSL_VERSION_NUMBER

the same happens with a fresh rails application, add those gems from the gist to the Gemfile and start rails

$ jruby -S rails server

and it fails with the same error. the workaround here is to add a require 'openssl' before the Bundler.require statement.

the gist gives the steps to reproduce it
https://gist.github.com/anonymous/9394738

the background is the websphere rails app which sees the same errors, all loosely related to jruby/warbler#238, jruby/warbler#241, #1119 #1435 and all regarding websphere

@mkristian mkristian added this to the JRuby 1.7.13 milestone Jun 15, 2014
@mkristian mkristian added the openssl label Jun 15, 2014
@enebo enebo modified the milestone: JRuby 1.7.14, JRuby 1.7.13 Jun 24, 2014
@enebo enebo modified the milestone: JRuby 1.7.14, JRuby 1.7.15 Aug 27, 2014
@mkristian mkristian modified the milestone: JRuby 1.7.17, JRuby 1.7.15 Nov 10, 2014
@mkristian
Member

it look like I can not reproduce this anymore, better close it now.

@rtyler
rtyler commented Nov 10, 2014

Should this be closed now?

@mkristian
Member

:)

@mkristian mkristian closed this Nov 10, 2014
@mkristian
Member

well, there is still an issue with some classloaders and default gems but this one I just can not reproduce it anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment