I am having problems with remote JMX working in JBoss 4.2.0, EAP. I have some Java OOM errors in my application and I am trying to configure this specifically to run VisualVM against it.
JBoss works against JDK 1.5
I tried to get this to work by adding the following to my JAVA_OPTS at startup (with a line extension here for readability):
-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl
-Djboss.platform.mbeanserver
-Dcom.sun.management.jmxremote.port=6789
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
When I start JBoss, I see entries in boot.log indicating that JMX is enabled on port 6789 and that auth and ssl are set to false. However, netstat shows nothing on port 6789, and I cannot connect to the telnet port. Unsurprisingly, VisualVM also cannot connect (it works both locally and remotely).
By default, the / jmx-console context that ships with JBoss seems to load fine if that matters.
Is something missing here? Was remote JMX support added later or something like that?
EDIT: I forgot to mention that JBoss works with an SSL connector, so I, for example, access the jmx console through https: // localhost: 8888 / jmx-console . Perhaps this affects the JMX connection?
source
share