JBoss Community Archive (Read Only)

JBoss AS 7.0

JMX subsystem configuration

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

<subsystem xmlns="urn:jboss:domain:jmx:1.0">
    <jmx-connector registry-binding="jmx-connector-registry" 
<socket-binding-group name="standard-sockets" default-interface="public">
    <socket-binding name="jmx-connector-registry" port="1090"/>
    <socket-binding name="jmx-connector-server" port="1091"/>

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

import javax.management.MBeanServerConnection;
import javax.management.remote.JMXConnector;
import javax.management.remote.JMXConnectorFactory;
import javax.management.remote.JMXServiceURL;

public class JMXExample {

    public static void main(String[] args) throws Exception {
        //Get a connection to the JBoss AS MBean server on localhost
        String host = "localhost";
        int port = 1090;
        String urlString = System.getProperty("jmx.service.url", 
            "service:jmx:rmi:///jndi/rmi://" + host + ":" + port + "/jmxrmi");
        JMXServiceURL serviceURL = new JMXServiceURL(urlString);
        JMXConnector jmxConnector = JMXConnectorFactory.connect(serviceURL, null);
        MBeanServerConnection connection = jmxConnector.getMBeanServerConnection();

        //Invoke on the JBoss AS MBean server
        int count = connection.getMBeanCount();

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



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


Shows what is bound in JNDI


This collection of MBeans exposes management operations on JBoss Modules classloading layer. It is useful for debugging dependency problems arising from missing module dependencies

JBoss.org Content Archive (Read Only), exported from JBoss Community Documentation Editor at 2020-03-13 13:19:55 UTC, last content change 2011-07-07 14:11:25 UTC.