Tomcat Web Hosting Blog - Java, JSP, EJB, Hibernate

Chapter 16: Monitoring and Managing Tomcat with JMX Attribute Name Read/Write Type maxAllocateIterations spareNotFoundEntries cacheSize desiredEntryAccessRatio R/W R/W RO R/W int int int long ThreadPool The following table shows attributes associated with the ThreadPoolobject. Attribute Name Read/Write Type modelerType name minSpareThreads currentThreadsBusy daemon threadStatus sequence currentThreadCount maxSpareThreads maxThreads threadParam R/W R/W R/W RO R/W RO RO RO R/W R/W RO java.lang.String java.lang.String int int boolean java.lang.String[] int int int int java.lang.String[] Accessing Tomcat 6 s JMX Support via the Manager Proxy The Manager application (featured in Chapter 8 ) has a JMX proxy that can be used to interact with Tomcat s agent level directly. The proxy enables the monitoring of Tomcat components through the exposed MBeans. It also enables you to read the value of an MBean attribute, or change/set the value of writable MBean attributes. Figure 16-7 illustrates the operation of the JMX proxy. In Figure 16-7 , notice that the Manager application provides an HTML-based interface to the JMX MBean server, acting as an HTTP protocol adapter for the agent. The Manager application adds essential value in this scenario. It provides querying capabilities and will authenticate the user before granting access to the JMX proxy. Architecturally, because the manager JMX proxy actually runs within the same JVM as the Tomcat server, it can be viewed as a part of Tomcat s agent-level implementation. As mentioned previously, it acts as an HTTP protocol adapter.

For reliable and cheap web hosting services please check tomcat web hosting website.