OpenSSL::Cipher#random_iv Regression in 18.104.22.168 #4857
I have java set to use
The text was updated successfully, but these errors were encountered:
This seems to only occur when installing with RVM. When downloading and running from the included binary file it's working as expected. I'm puzzled as to why this would be the case.
Run the slow case with the following flag, so we can get some lower-level profiling:
If it's running that long it should be pretty obvious what it's spending its time on.
The main differences I can think of when installing via RVM would be the default gem set and the jruby-launcher gem. The latter is our native executable; to be portable, the tarball does not normally include it. RVM installs it when installing JRuby, since there's some use cases that don't work with the bash script.
But this doesn't give me any idea why there's such a big difference.
this seems like (yet another) depleting entropy issue. although you have java.security setup properly
The workaround there is what I'm using for JRuby 9.1.15 in the launchers: specify the path in such a way that the JDK can't detect it, such as
I'm getting the following from visualvm
Here's the sample output when running
Ah-ha! All those
This seems like it could be related, but I don't understand why it would work with our tarball and not with an RVM install.
Here's another interesting article that shows how to test whether entropy is being exhausted, along with other tips: https://liuzy163.wordpress.com/2015/03/20/tomcat-server-slow-due-to-blocked-seedgenerator-thread-on-insufficient-random-number-on-linux/
I think I know the connection!
You are not running 22.214.171.124, which includes the urandom change in the jruby bash script. However when you install from RVM, it installs jruby-launcher...which does have the urandom change.
So something about the way I'm setting security to use urandom is wrong. I confirmed I'm seeing these threads locally, and my local startup is also slower (I thought I just messed up my env).
I would recommend doing installing the 1.1.2 version of jruby-launcher gem, which should overwrite the one with the urandom tweak. I'll figure out what's wrong with it and spin a new release.
@headius you, sir, are the man! That seems to have done it.