Question about issue

smarlow Jul 8, 2009 5:29 PM

JOPR currently expects to use the Sun jmxremote support with AS 5.x, however, that doesn't seem to work when the following options are added to run.conf:

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote"
JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"

There seems to be at least two issues at play here:

1. The org.jboss.system.server.jmx.MBeanServerBuilderImpl class is not on the system classpath, so the Sun jdk classes cannot reference it.

2. Even if MBeanServerBuilderImpl became accessible via the system classpath, it seems that we need a different kind of bridge between the Sun JDK mbeanserver and the MC hosted mbean server.

Do we need a new MBeanServerBuilderImpl and LazyMBeanServer implementation that can provide a bridge between the MC and the Sun jdk jmx code?

Ideas?

1. Re: Question about issue

smarlow Jul 8, 2009 5:53 PM (in response to smarlow)

The subject should of included "JBAS-6185 JBoss MBeans in JConsole no longer works"
Actions
2. Re: Question about issue

smarlow Jul 9, 2009 11:44 AM (in response to smarlow)

It looks like our current LazyMBeanServer should be able to handle this. There may be a few small changes needed but I will go ahead with moving the MBeanServerBuilderImpl + LazyMBeanServer onto the system classpath.
Actions

Go to original post