Monitor JBossAS using JConsole
https://access.redhat.com/kb/docs/DOC-52924 Monitoring JBoss AS using JConsole Article ID: 52924 - Created on: Sep 9, 2009 10:25 AM - Last Modified: Mar 28, 2011 11:28 AM Issue What configuration is required to enable monitoring of JBoss AS instances using JConsole Environment JDK 1.6, 1.5 Enterprise Application Platform (EAP) 4.2.0 4.3.0 5.0.0 Resolution Add the following config parameters to run.conf JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false" JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=3001" JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl" The above example has authentication set to false. For production systems, enabling authentication is recommended to prevent unauthorised access. See the Sun online documentation http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html for more details. For remote access specify hostname:port or jmx url service:jmx:rmi:///jndi/rmi://hostname:port/jmxrmi Where port is -Dcom.sun.management.jmxremote.port If after these configuration changes jconsole does not show jboss as an available local process to monitor, try to reach jboss as a remote process e.g. localhost:3001. N.B To monitor multiple instances of JBoss AS, running on the same server, each instance will need to have it's own run.conf or jvm startup options. Otherwise you will get an exception regarding the jmxremote.port. This is a limitation in the Sun implementation. See bug_id=6425769 There is a known issue regarding this config setting not working in EAP 4.3.0 CP06. See DOC-18442 for workaround