Jconsole: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 41: Line 41:
* [[JMX_Access_to_Domain_Mode_EAP_6_Server_Node#URL|For EAP 6 Domain Mode Server Node]]
* [[JMX_Access_to_Domain_Mode_EAP_6_Server_Node#URL|For EAP 6 Domain Mode Server Node]]
* [[JMX_Access_To_Standalone_EAP_7#URL|For Standalone EAP 7]]
* [[JMX_Access_To_Standalone_EAP_7#URL|For Standalone EAP 7]]
* [[JMX_Access_to_EAP_7_Host_Controller#URL|For EAP 7 Host Controller]]

Revision as of 01:18, 19 October 2016

Internal

Overview

Configuring jconsole to Connect over JMX to a WildFly Instance

jconsole Classpath and Startup Options

jconsole must be started with the following classpath:

-Djava.class.path=${JAVA_HOME}/lib/jconsole.jar:${JAVA_HOME}/lib/tools.jar:${JBOSS_HOME}/bin/client/jboss-cli-client.jar

jconsole must also receive the following system property on command line:

-Dmodule.path=${JBOSS_HOME}/modules

The full command line is:

jconsole \
 -J-Djava.class.path=${JAVA_HOME}/lib/jconsole.jar:${JAVA_HOME}/lib/tools.jar:${JBOSS_HOME}/bin/client/jboss-cli-client.jar \
 -J-Dmodule.path=${JBOSS_HOME}/modules

Connect to a "Remote Process"


Jconsole Remote Process.png

Use the following URLs: