« Chapter 16: Monitoring and Managing Tomcat with JMX
Chapter 16: Monitoring and Managing Tomcat with JMX »

Chapter 16: Monitoring and Managing Tomcat with JMX

Chapter 16: Monitoring and Managing Tomcat with JMX The output of the query will be similar to what is shown in Figure 16-10 . Figure 16-10: Querying for Tomcat 6 s ThreadPool MB ean name The current value of the maxThreadsattribute for the first ThreadPoolis 150. It will be changed to 200. Now, the full name of the MBean for this first threadpool is visible from the query output as follows: Catalina:type=ThreadPool,name=http-8080 Next, by consulting the Tomcat 6 MBeans description listing in this chapter, you can determine that the maxThreads attribute is a writable property. Finally, the URL for the set operation is as follows (type the entire URL on one line): http://:
/manager/jmxproxy/?set= Catalina: type=ThreadPool,name=http-8080&att=maxThreads&val=200 Upon successful operation, the output is similar to what is shown in Figure 16-11 . If you try to modify a read-only attribute, you will receive a message reporting an attribute not found exception.

If you looking for unlimited one inclusive web hosting plan please check unlimited web hosting website.

This entry was posted on Tuesday, October 27th, 2009 at 11:21 am and is filed under tomcat. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.

Comments are closed.