Running rake in a Rails 3.1.1 app with debug (-d) on via rvm/jruby gives java.lang.ClassNotFoundException: rubygems.defaults.OperatingSystemService

output from "gem list"

got the same error when running my ruby application. But apart from the error the
application works fine:
java.lang.ClassNotFoundException: rubygems.defaults.OperatingSystemService
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at org.jruby.util.JRubyClassLoader.findClass(JRubyClassLoader.java:86)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
...
java.lang.ClassNotFoundException: rubygems.defaults.JrubyNativeService
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

trigger: require 'date'

@chris: can you give this ticket a higher priority? Because in my case this bug prevents using the new version for production

Would love to Alex - but I cant see a way to change the priority Not being able to use debug is a production stopper - sounds strange to me

Ouch - feel free to "Clone" this one under the more actions option and set the priority higher on the new one - we can then say this one has been superseded. Strange that I cannot edit it - must be missing the edit button somewhere or just dont have the privileges to edit

Same error with option '-d'
eg. Rails, any other standalone-program,

but with option '--debug' all works fine.

Hello -
I'm not sure if there is a problem here. You are asking JRuby to print debugging output with -d, and it is. Checking to see if a class is available to load using java.lang.Class.forName() will raise a ClassNotFoundException, but if it's handled upstream, then that may be the desired behavior. Also, I was not able to get rake to blow up using "require 'date'" (at least on Windows).

The output seems to be coming from org.jruby.runtime.load.LoadService.java:

protected boolean tryLoadingLibraryOrScript(Ruby runtime, SearchState state) {
...

// this only re-raises if the exception is an instance of 
// org.jruby.exceptions.RaiseException
// ClassNotFoundException is not an instance of RaiseException
reraiseRaiseExceptions(e); 

// if debugging is turned on, then print out a stacktrace.                           

if(runtime.getDebug().isTrue()) e.printStackTrace(runtime.getErr());
...
}

Given that the method is named "tryLoadingLibraryOrScript", I'm guessing that it's OK that exceptions are being thrown further up the stack.

Hope this helps!
Dave

Dave Parfitt is correct. This is expected debugging output.

JRuby, in debug mode, will log classes that fail to be looked up. Some of these happen during JRuby's normal boot process. The exception you are seeing is nothing unusual.

There might be an argument to have a "more debuggy" flag that turns on JRuby-specific debug logging. I'm not going to make that argument

Thanks for clarifying that. I had "assumed" that it was failing from that output. To be honest, not sure what I was trying to do when I got this error, seems I forgot to mention that in the bug report.