JMX Monitoring of GlassFish Servers
By Tim Quinn-Oracle on Sep 26, 2012
or into the New Connection dialog of jconsole:
(The full string is truncated in the on-screen display, but if you copied from the server.log and pasted into the form it should all be there.)
The examples above are for a DAS, and your host will probably be different. The server.log files for other GlassFish servers (instances) will have similar log entries giving the JMX connection string to use for those processes. Look for the host and/or port to be different.
Once you have connected you have normal access to all the JVM statistics and controls, such as threads, memory, etc.
Note a few things about security:
- Here we've assumed you are using the default admin username and password. If you are not, just enter a valid admin username and password for your installation.
- You can use JMX clients that support MBeans to view the GlassFish configuration. When you connect to the DAS, you can also change that configuration, but when connected to an instance you can only view configuration.
- To use a JMX client on one system to connect to a GlassFish server running on another system, you need to enable secure admin if you have not already done so:
- asadmin change-admin-password (respond to the prompts)
- asadmin enable-secure-admin
- asadmin restart-domain (as prompted in the output from enable-secure-admin)