Monitor JK-1.2.40 connection status through jkstatus

/* Through jkstatus monitoring JK-1.2.40 connection status * running * configuration jkstatus * 0) This article is based on the integration of Apache and tomcat using JK, the integration process see http://blog.csdn.net/jadyer/article/details/39613523 * 1) in workers. add two lines to the properties file: worker. list = status (actually worker. list = status, Tomcat) and worker. status. type = status * 2) add a line under the <directory/> label in the httpd-vhosts.conf file: jkmount/jkstatus status * 3) Restart Apache and access HTTP in the browser: // 192.168.0.103/jkstatus, the default access does not require the password * optional * configure the password to access jkstatus * 1) modify the httpd-vhosts.conf file, add the following content under the <directory/> label * <location/jkstatus> * options Multiviews * authtype basic # basic verification * authname "auther Center" # the pop-up box prompts * authuserfile CONF/. htpasswd # password storage location * require valid-user granted # only. users in the htpasswd file can enter * </location> * 2) generate the password file * run the command [/APP/Apache/bin/htpasswd-C/APP/Apache/CONF /. htpasswd admin], which is used to generate a password file containing the user admin *. At the same time, you will be asked to enter the new user admin password twice, finally, you can see the generated password file through [LS-Al] (it is a hidden file, you need-a to see) * 3) change the password * htpasswd-M. htpasswd username * 4) Delete the user * htpasswd-D. htpasswd username * 5) The last restart Apache can be * done * @ create Sep 27,201 4 3:36:34 * @ author Xuan Yu 
Monitor JK-1.2.40 connection status through jkstatus