Hi!

>However, the JVM believes that it is the MBeanClassLoader which loaded
these classes and >creates a cache record from the MBeanClassLoader to the
ejb home interface. 

This is really strange, because the VM (or maybe: the MBeanClassLoader)
shouldn´t cache such information except when doing a
ClassLoader.defineClass() call. 

I remember seeing some really inconsistent behaviour of the JVM when using
Class.forName() instead of
Thread.currentThread().getContextClassLoader().loadClass() in the unified
classloader scheme. I think that Class.forName() does a few obscure things
(in opaque native code) including caching wrong location information ...
Could you check whether
there are such calls in the SUN JMXRI?

CGJ


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to