Jconsole: Difference between revisions
Jump to navigation
Jump to search
| Line 24: | Line 24: | ||
jconsole \ | jconsole \ | ||
-J-Djava.class.path=${JAVA_HOME}/lib/jconsole.jar:${JAVA_HOME}/lib/tools.jar:${JBOSS_HOME}/bin/client/jboss-cli-client.jar \ | -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 | -J-Dmodule.path=${JBOSS_HOME}/modules | ||
</pre> | </pre> | ||
Revision as of 21:00, 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:
-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"
Use the following URLs: