Skip to end of metadata
Go to start of metadata

The JMX subsystem sets up a JMX connector so that invocations can be done on the JMX MBean server from outside the JVM

To use the connector you can access it in the standard way:

You can also connect using jconsole. In addition to the standard JVM MBeans, the JBoss AS 7 MBean server contains the following MBeans:

JMX ObjectName Description
jboss.msc:type=container,name=jboss-as Exposes management operations on the JBoss Modular Service Container, which is the dependency injection framework at the heart of JBoss AS 7. It is useful for debugging dependency problems, for example if you are integrating your own subsystems, as it exposes operations to dump all services and their current states
jboss.naming:type=JNDIView Shows what is bound in JNDI
jboss.modules:type=ModuleLoader,name=* This collection of MBeans exposes management operations on JBoss Modules classloading layer. It is useful for debugging dependency problems arising from missing module dependencies
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jun 26, 2012

    For urn:jboss:domain:jmx:1.1 it is

    with use-management-endpoint false means use remoting endpoint and true means management endpoint.

  2. Dec 27, 2013

    For urn:jboss:domain:jmx:1.1 it worked for me with:

  3. Apr 20, 2014

    If i want to set up JMX in jboss eap 6, what are the changes i need to do in the JMX subsystem in domain mode?

    <subsystem xmlns="urn:jboss:domain:jmx:1.2">
                    <expose-resolved-model/>
                    <expose-expression-model/>
    </subsystem>