Page created: 22 Jul 2020 |
Page updated: 1 Feb 2021
Before you can access JConsole, you must configure and enable the JMX Connection Handler for the Directory Proxy Server using the dsconfig tool. See Configuring the JMX Connection Handler and Alert Handler.
To invoke the JConsole executable, type jconsole on the command line. If JDK_HOME is not set in your path, you can access JConsole in the bin directory of the JDK_HOME path.
To run JConsole:
Use JConsole to open the Java Monitoring and Management Console.
You can also run JConsole to monitor a specific process ID for your application:
jconsole PID. Or you can run JConsole remotely using:
$ jconsoleNote: If SSL is configured on the JMX Connection Handler, you must specify the Directory Proxy Server jar file in the class path when running jconsole over SSL. For example, run the following jconsole command:
$ jconsole \ -J-Djavax.net.ssl.trustStore=/path/to/certStores/truststore \ -J-Djavax.net.ssl.trustStorePassword=secret \ -J-Djava.class.path=$SERVER_ROOT/lib/PingDirectoryProxy.jar:/Library/Java/JavaVirtualMachines/jdk-version.jdk/Contents/Home/lib/jconsole.jar
On the Java Monitoring & Administrative Console, click
Local Process, and then click the
PID corresponding to the directory server.
Review the resource monitoring information.