On Fri, 2010-01-15 at 09:32 +0100, Adrian Brock wrote:
On Thu, 2010-01-14 at 12:45 +0200, Dimitris Andreadis wrote:
> It would be interesting to see if their is any performance difference using our or
JDK's
> mbeanserver implementation.
>
It doesn't seem to make an appreachable difference for the boot time
or running the basic tests. It might show a difference if you
stressed an MBeanServer.invoke() like we do in EJB2?
Anyway, I've added this to trunk now. You can try it with
./run.sh
-Djavax.management.builder.initial=org.jboss.jmx.mbeanserver.JBossMBeanServerBuilder
I seem to have a bug with the remote jmx usage and classloading
which I need to investigate. e.g. using the jmx-remoting.sar
classloader instead of the jmx deployment's classloader.
I've fixed the classloader problem.
We might want to run the full testsuite over it at some point when the
testsuite has been tidied up?
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx