Jconsole: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 38: Line 38:


* [[JMX_Access_to_Standalone_EAP_6#URL|For Standalone EAP 6]]
* [[JMX_Access_to_Standalone_EAP_6#URL|For Standalone EAP 6]]
* [[JMX_Access_to_EAP_6_Host_Controller#URL|For EAP 6 Host Controller]]
* [[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_EAP_7_Host_Controller#URL|For EAP 7 Host Controller]]
* [[JMX_Access_to_Domain_Mode_EAP_7_Server_Node#URL|For EAP 7 Domain Mode Server Node]]

Latest revision as of 05:56, 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: