Author: fschumacher
Date: Tue Dec 6 19:53:09 2016
New Revision: 1772947
URL: http://svn.apache.org/viewvc?rev=1772947&view=rev
Log:
Fix typo
Modified:
tomcat/trunk/webapps/docs/monitoring.xml
Modified: tomcat/trunk/webapps/docs/monitoring.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/monitoring.xml?rev=1772947&r1=1772946&r2=1772947&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/monitoring.xml (original)
+++ tomcat/trunk/webapps/docs/monitoring.xml Tue Dec 6 19:53:09 2016
@@ -1157,7 +1157,7 @@ Wait for server connection and that clus
<p>
A perfect example of JMX overkill can be seen in the case of popular
- server-monitoring software such as Nagios or Ichinga: if you want to
+ server-monitoring software such as Nagios or Icinga: if you want to
monitor 10 items via JMX, you will have to launch 10 JVMs, make 10 JMX
connections, and then shut them all down every few minutes. With the
JMXProxyServlet, you can make 10 HTTP connections and be done with it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
