You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# shell-out-test.rbJRuby.runtime.instance_config.run_ruby_in_process=trueputs"starting script and sleeping for 5 seconds"sleep10puts"shelling out for 10 seconds"`ruby -e 'sleep 10'`puts"done shelling out, sleeping another 5 seconds"sleep5
In one terminal run watch 'ps aux |grep [j]ava'
In another, run ruby shell-out-test
Observe that two instances of Java processes are created.
I /think/ this means the feature isn't working? Or maybe even when reusing the JVM there is some sort of OS-level presence for ruby invocation?
➔ java -version
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
➔ jruby --version
jruby 1.7.19 (1.9.3p551) 2015-01-29 20786bd on Java HotSpot(TM) 64-Bit Server VM 1.7.0_45-b18 +jit [darwin-x86_64]
The text was updated successfully, but these errors were encountered:
jjb
changed the title
reusing JVM instance when shelling out is broken
run_ruby_in_process is broken
Mar 24, 2015
I have a collection of maintenance scripts I want to run nightly, and I want to invoke them from a master script.
I was going to reimplement this system using background workers eventually anyway, so consider this a vote to officially stop supporting this feature :)
To observe:
In one terminal run
watch 'ps aux |grep [j]ava'
In another, run
ruby shell-out-test
Observe that two instances of Java processes are created.
I /think/ this means the feature isn't working? Or maybe even when reusing the JVM there is some sort of OS-level presence for ruby invocation?
The text was updated successfully, but these errors were encountered: