You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by kk...@apache.org on 2010/02/25 10:32:08 UTC
svn commit: r916196 - in /tomcat/trunk/webapps/docs: html-manager-howto.xml
manager-howto.xml
Author: kkolinko
Date: Thu Feb 25 09:32:08 2010
New Revision: 916196
URL: http://svn.apache.org/viewvc?rev=916196&view=rev
Log:
correct a typo
Modified:
tomcat/trunk/webapps/docs/html-manager-howto.xml
tomcat/trunk/webapps/docs/manager-howto.xml
Modified: tomcat/trunk/webapps/docs/html-manager-howto.xml
URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/html-manager-howto.xml?rev=916196&r1=916195&r2=916196&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/html-manager-howto.xml (original)
+++ tomcat/trunk/webapps/docs/html-manager-howto.xml Thu Feb 25 09:32:08 2010
@@ -558,11 +558,11 @@
StandardHost implementation. It will not work if a custom host is used that
does not extend StandardHost.</p>
-<p>Explicitely triggering a full garbage collection from Java Code is documented
+<p>Explicitly triggering a full garbage collection from Java Code is documented
to be unreliable. Furthermore, depending on the JVM used, there are options to
disable explicit GC triggering, like <code>-XX:+DisableExplicitGC</code>.
If you want to make sure, that the diagnostics were successfully running a full GC,
-you will need to check using tools like GC logging, JConsole or simlar.</p>
+you will need to check using tools like GC logging, JConsole or similar.</p>
</section>
Modified: tomcat/trunk/webapps/docs/manager-howto.xml
URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/manager-howto.xml?rev=916196&r1=916195&r2=916196&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/manager-howto.xml (original)
+++ tomcat/trunk/webapps/docs/manager-howto.xml Thu Feb 25 09:32:08 2010
@@ -908,11 +908,11 @@
StandardHost implementation. It will not work if a custom host is used that
does not extend StandardHost.</p>
-<p>Explicitely triggering a full garbage collection from Java Code is documented
+<p>Explicitly triggering a full garbage collection from Java Code is documented
to be unreliable. Furthermore, depending on the JVM used, there are options to
disable explicit GC triggering, like <code>-XX:+DisableExplicitGC</code>.
If you want to make sure, that the diagnostics were successfully running a full GC,
-you will need to check using tools like GC logging, JConsole or simlar.</p>
+you will need to check using tools like GC logging, JConsole or similar.</p>
<p>If this command succeeds, you will see a response like this:</p>
<source>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org