The JMX subsystem registers a service with the Remoting endpoint so that remote access to JMX can be obtained over the exposed Remoting connector.
This is switched on by default in standalone mode and accessible over port 9999 but in domain mode is switched off so needs to be enabled - in domain mode the port will be the port of the Remoting connector for the AS instance to be monitored.
To use the connector you can access it in the standard way using a service:jmx URL:
You also need to set your classpath when running the above example. The following script covers Linux. If your environment is much different, paste your script when you have it working.
You can also connect using jconsole.
|If using jconsole use the jconsole.sh and jconsole.bat scripts included in the bin folder of the AS distribution as these set the classpath as required to connect over Remoting.|
In addition to the standard JVM MBeans, the JBoss AS 7 MBean server contains the following MBeans:
|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|