[Adding Richard Hall and dev alias]
Ok, so the root cause is upgrade to Felix 1.6.0. Not sure if
FELIX-851[2] is causing this to happen. Basically Felix
ModuleClassLoader is the parent class loader of the URLClassLoader using
which all of jruby runtime classes are loaded. There is some logic in
felix where it tries to determine the enclosing class of inner classes
and thats where a ClassCircularityError is reported.
Although it is ignored from inside Felix but somehow this behavior of
determining if a class being loaded is requested by the one from an OSGi
bundle or not is causing certain instability that latter on results in
to more of ClassCirculatoryError. There is JDK bugs [1] reported on jdk
5 and 6 as well.
Here is the felix stack trace, where this error is reported:
http://pastie.org/451117
This is the code in felix 1.6.0 branch where this error occurs:
org.apache.felix.framework.searchpolicy.ModuleImpl:1287 (felix 1.6.0
codebase)
if (getEnclosingClassMethod != null)
{
try
{
Class enclosing = (Class)
getEnclosingClassMethod.invoke(clazz, null);
clazz = (enclosing != null) ? enclosing : clazz;
}
catch (Throwable t)
{
// Ignore everything and use original class.
}
}
Here is how I am loading classes:
I have a jar file at: glassfish/modules/grizzly-jruby.jar.
I use a URLClassLoader to load this jar file and also external jars
files (part of application/jruby jars). The classes are loaded
reflectively using this URLClassLoader. The parent of this
URLClassLoader is ModuleClassLoader from felix.
The deployment fails with ClassCirculatoryError. I would like to know if
there is a bug in felix 1.6 code or if I need to do something else to
workaround this error. Please note that the whole thing worked with the
previous felix version 1.2.2 of glassfish b43.
Due to this failure I am not able to proceed further and not sure how I
can integrate JRuby monitoring code as I cant test it on v3 trunk.
-vivek,
[1]
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6508296
[2]
http://www.mail-archive.com/dev@felix.apache.org/msg06806.html
Vivek Pandey wrote:
> There is JRuby QL failure:
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=7648.
>
> You might recall how jruby compiler runtime is initiated by jruby
> container. Basically, based on where jruby install (jruby.home is), a
> URLClassLoader is created using the jruby install jars. This
> URLClassLoader is used to start of JRuby runtime by reflection.
>
>
> URL[] urls = findJRubyJars();
> ClassLoader cl = new URLClassLoader(urls,
> JRubyApplication.class.getClassLoader());
>
> Class<?> c =
> cl.loadClass("com.sun.grizzly.jruby.RubyRuntime");
> this.jRubyRuntime = c.getConstructor(Properties.class,
> String.class,
> String.class).newInstance(deploymentContext.getAppProps(), railsRoot,
> contextRoot);
> this.adapter = (com.sun.grizzly.tcp.Adapter)
> c.getMethod("getAdapter").invoke(jRubyRuntime);
> startJRubyGrizzlyAdapter();
>
> See method initJRubyGrizzlyAdapter() and rest of the code at:
> http://pastie.org/450451
>
> for some reason with b45 onward and latest v3 trunk, I see one thing
> that the previous v3 build b43, used to have ContentClassLoader that
> loaded the JRubyApplication and now in trunka dn b45, there is
> ModuleClassLoader. Not sure whats going on that is causing such
> ClassCirculatoryError.
>
>
> ---------
> java.lang.ClassCircularityError:
> org/jruby/lexer/yacc/RubyYaccLexer$LexState
> Apr 17, 2009 4:02:40 PM SEVERE: at
> org.jruby.lexer.yacc.RubyYaccLexer.yylex(RubyYaccLexer.java:917)
> ---------
>
> See the details stack trace: http://pastie.org/450344
>
> Due to this error, JRuby/Rails etc. are not working on trunk. Probably
> you would have some idea as to whats going on.
>
> thanks,
>
> -vivek.
>