Tomcat performance monitoring tool probe Quick Start

Tomcat version: 6.0.41

Probe version: 2.3.3

One, Tomcat does not have a default user account, so you need to add the Tomcat user account first

Modify $catalina_home/conf/tomcat-users.xml:

<tomcat-users>
<!--user Role--
<role rolename= "manager"/>
<!--user account
--< User username= "admin" password= "admin" roles= "manager"/>
</tomcat-users>

Then restart Tomcat

Second, deploy probe applications

Mode 1:

Throw the Probe.war under the $catalina_home/webapps and restart Tomcat.

Mode 2:

Login to the Tomcat Welcome page (ex: http://127.0.0.1:8080/)

It is important to note that the $catalina_home/webapps contains the root folder (Welcome page) and the Manager folder (Tomcat Management page), which you would like to remove from your production environment. If these two folders do not exist, simply copy the two folders to $catalina_home/webapps and restart Tomcat

The path to the root app is "/" and will cause the app to start failing if the path to the other web app you are deploying is also "/"

The application configuration $CATALINA _home/conf/server.xml is as follows:

<context docbase= "/home/sean/web/webroot" path= "/" reloadable= "false" >
	<resourcelink global= "Database "Name=" Database "type=" Javax.sql.DataSource "/>
</Context>

This will cause the app to start failing (path conflict, where you need to modify the value of the Path property, such as: Path= "/app")

The account is the previously configured Admin/admin, and all Web apps under Tomcat can be seen after successful login

Select Probe.war, then click Deploy, and the app will be included in Tomcat's management scope:

You can now enter the probe page (for example: Http://127.0.0.1:8080/probe, if you need a password, or admin/admin)

Third, monitor Tomcat performance with probe

1. Monitor Application Status

Tap into each app to see more detailed monitoring information

2, monitoring database connection

3. Deploy the App

4, monitoring log information

You can view all the log information for Tomcat itself and the log information that Tomcat manages to print the app, and filter the required log information based on the log level

5. Monitor Cluster operation status

Support for tomcat5.5.x cluster monitoring only

6. Monitor the status of all threads

7. Monitor and Count Tomcat connections