Chapter 16: Monitoring and Managing Tomcat with JMX
Chapter 16: Monitoring and Managing Tomcat with JMX Click the Connect button after selecting the Tomcat JVM. jconsole connects to the Tomcat JVM and displays all sorts of JMX data exposed by the Java VM itself. Locating the Tomcat 6 Exposed MB eans The jconsole displays a lot of exposed metrics courtesy of the fully instrumented JVM. You can find a lot more information about jconsole and the other management and monitoring tools in the JDK by visiting the following URL: http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html To locate the MBeans exposed by Tomcat in the jconsole GUI, click the MBeans tab. In this tab, you see JVM MBeans as well as those associated with Tomcat. Those exposed by Tomcat 6 are under the keys named Catalinaand Users. Figure 16-14 shows jconsole with the Tomcat 6 exposed ThreadPool information. Note the http-8080 and jk-8009 threadpools, the same as the one you saw earlier in the Manager JMXProxy example. jconosle just provides a way to access the same set of Tomcat 6 JMX MBeans. Figure 16-14: Tomcat Exposed MB eans viewed through the jconsole utility If you examine the list of exposed manageable elements under the Catalinakey in jconsole, you see that it correspond to the list of JMX manageable elements documented in this chapter. Using jconsole, you can find and monitor the current values of their attributes.
For high quality java hosting services please check java web hosting website.