Skip to content
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

openssl issue with rails and installed default gems #1549

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

openssl issue with rails and installed default gems #1549

mkristian opened this issue Mar 6, 2014 · 4 comments
Labels
Milestone

Comments

@mkristian
Copy link
Member

@mkristian mkristian commented Mar 6, 2014

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
@enebo enebo added this to the JRuby 1.7.14 milestone Jun 24, 2014
@enebo enebo removed this from the JRuby 1.7.13 milestone Jun 24, 2014
@enebo enebo removed this from the JRuby 1.7.14 milestone Aug 27, 2014
@enebo enebo added this to the JRuby 1.7.15 milestone Aug 27, 2014
@mkristian mkristian added this to the JRuby 1.7.17 milestone Nov 10, 2014
@mkristian mkristian removed this from the JRuby 1.7.15 milestone Nov 10, 2014
@mkristian
Copy link
Member Author

@mkristian mkristian commented Nov 10, 2014

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

@rtyler
Copy link

@rtyler rtyler commented Nov 10, 2014

Should this be closed now?

@mkristian
Copy link
Member Author

@mkristian mkristian commented Nov 10, 2014

:)

@mkristian mkristian closed this Nov 10, 2014
@mkristian
Copy link
Member Author

@mkristian mkristian commented Nov 10, 2014

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
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants