Jconsole: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 7: Line 7:
==jconsole Classpath and Startup Options==
==jconsole Classpath and Startup Options==


Start jconsole with the following classpath:
jconsole must be started with the following classpath:


<pre>
<pre>
Line 13: Line 13:
</pre>
</pre>


For example, if your jconsole/JDK has been installed under <tt></tt>, the command line should be:
jconsole must also receive the following system property on command line:


<pre>
<pre>
jconsole -J-Dclasspath=${JAVA_HOME}/lib/jconsole.jar:${JAVA_HOME}/lib/tools.jar:${JBOSS_HOME}/bin/client/jboss-cli-client.jar
-Dmodule.path=$JBOSS_HOME/modules
</pre>
 
The full command line is:
 
<pre>
jconsole \
  -J-Dclasspath=${JAVA_HOME}/lib/jconsole.jar:${JAVA_HOME}/lib/tools.jar:${JBOSS_HOME}/bin/client/jboss-cli-client.jar \
  -J-Dmodule.path=$JBOSS_HOME/modules
</pre>
</pre>



Revision as of 20:55, 18 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:

$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-Dclasspath=${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"

Use the following URLs: