Hey
Justin Forder wrote:
> >The problem is all the classes that are added to the JMX classloader. At
> >some point RMI wants to use the classloader and look for some class.
> >Since the classloader is absolutely stuffed with classes this takes a
> >very very very long time. So, by simply removing the ClassPathExtension
> >MBeans I was able to get the call latency down from 80-100 ms to <10 ms.
>
> Is the classloader using linear search? If so, can that be fixed? (I
> would regard it as a bug.)
This is the MLet classloader that comes with JMX so there's nothing I/we
can do about it.
> >Solution? Should we try to partition the classes more (by adding more
> >MLet classloaders)? That would probably be the cleanest solution, and
> >would also make it possible to upgrade the system on the fly since only
> >the affected MBean could be removed/updated/restarted.
>
> That spinoff would be good, but takes the pressure off getting
> acceptable classloader performance.
True.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
