Author: markt
Date: Tue Jan 12 22:06:38 2010
New Revision: 898545
URL: http://svn.apache.org/viewvc?rev=898545&view=rev
Log:
Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=48530
Add info on the Server Status page to the Manager How-To
Based on a patch by Arnaud Espy
Modified:
tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml
tomcat/tc6.0.x/trunk/webapps/docs/manager-howto.xml
Modified: tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml?rev=898545&r1=898544&r2=898545&view=diff
==============================================================================
--- tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml (original)
+++ tomcat/tc6.0.x/trunk/webapps/docs/changelog.xml Tue Jan 12 22:06:38 2010
@@ -69,6 +69,15 @@
</update>
</changelog>
</subsection>
+ <subsection name="Webapps">
+ <changelog>
+ <add>
+ <bug>48530</bug>: Add information on the Manager Server Status page to
+ the Manager How-To in the documentation webapp. Based on a patch by
+ Arnaud Espy. (markt)
+ </add>
+ </changelog>
+ </subsection>
<subsection name="Other">
<changelog>
<fix>
Modified: tomcat/tc6.0.x/trunk/webapps/docs/manager-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/manager-howto.xml?rev=898545&r1=898544&r2=898545&view=diff
==============================================================================
--- tomcat/tc6.0.x/trunk/webapps/docs/manager-howto.xml (original)
+++ tomcat/tc6.0.x/trunk/webapps/docs/manager-howto.xml Tue Jan 12 22:06:38 2010
@@ -897,6 +897,52 @@
</subsection>
+<subsection name="Server Status">
+
+<p>From this link , you can view information about the server.</p>
+
+<p>First, you have the server and JVM version number, JVM provider, OS name
+and number followed by the architecture type.</p>
+
+<p>Second, there is several information about the memory usage of the JVM
+(available, total and max memory).</p>
+
+<p>Then, there is information about the Tomcat AJP and HTTP connectors.
+The same information is available for both of them :
+</p>
+<ul>
+ <li><p>Threads information : Max threads, min and max spare threads,
+ current thread count and current thread busy.</p></li>
+ <li><p>Request information : Max processing time and processing time,
+ request and error count, bytes received and sent.</p></li>
+ <li><p>A table showing Stage, Time, Bytes Sent, Bytes Receive, Client,
+ VHost and Request. All existing threads are listed in the table.
+ Here is the list of the possible thread stages :</p>
+ <ul>
+ <li><p><em>"Parse and Prepare Request"</em> : The request headers are
+ being parsed or the necessary preparation to read the request body (if
+ a transfer encoding has been specified) is taking place.</p></li>
+ <li><p><em>"Service"</em> : The thread is processing a request and
+ generating the response. This stage follows the "Parse and Prepare
+ Request" stage and precedes the "Finishing" stage. There is always at
+ least one thread in this stage (the server-status page).</p></li>
+ <li><p><em>"Finishing"</em> : The end of the request processing. Any
+ remainder of the response still in the output buffers is sent to the
+ client. This stage is followed by "Keep-Alive" if it is appropriate to
+ keep the connection alive or "Ready" if "Keep-Alive" is not
+ appropriate.</p></li>
+ <li><p><em>"Keep-Alive"</em> : The thread keeps the connection open to
+ the client in case the client sends another request. If another request
+ is recieved, the next stage will br "Parse and Prepare Requst". If no
+ request is received before the keep alive times out, the connection
will
+ be closed and the next stage will be "Ready".</p></li>
+ <li><p><em>"Ready"</em> : The thread is at rest and ready to be
+ used.</p></li>
+ </ul>
+ </li>
+</ul>
+</subsection>
+
</section>
<section name="Executing Manager Commands With Ant">
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
