Author: remm
Date: Wed Mar 29 03:49:10 2006
New Revision: 389768
URL: http://svn.apache.org/viewcvs?rev=389768&view=rev
Log:
- Document according to the current defaults.
Modified:
tomcat/container/tc5.5.x/webapps/docs/apr.xml
Modified: tomcat/container/tc5.5.x/webapps/docs/apr.xml
URL:
http://svn.apache.org/viewcvs/tomcat/container/tc5.5.x/webapps/docs/apr.xml?rev=389768&r1=389767&r2=389768&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/apr.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/apr.xml Wed Mar 29 03:49:10 2006
@@ -68,7 +68,7 @@
<p>
Requirements:
<ul>
- <li>APR 1.1+ development headers (libapr1-dev package)</li>
+ <li>APR 1.2+ development headers (libapr1-dev package)</li>
<li>OpenSSL 0.9.7+ development headers (libssl-dev package)</li>
<li>JNI headers from Java compatible JDK 1.4+</li>
<li>GNU development environment (gcc, make)</li>
@@ -128,22 +128,28 @@
<attribute name="firstReadTimeout" required="false">
<p>The first read of a request will be made using the specified timeout.
If no data is available
- after the specified time, the socket will be placed in the poller.
Setting this value to 0 will
- increase scalability, but will have a minor impact on latency (see the
related pollTime attribute).
- The default value is 100 (100ms). Note: on Windows, the actual value of
firstReadTimeout will
- be 500 + the specified value.</p>
+ after the specified time, the socket will be placed in the poller. The
value of this attribute is
+ in ms. Setting this value to 0 or -1 will
+ increase scalability by always using a poller to handle keepalive, but
will have a minor impact
+ on latency (see the related pollTime attribute). The difference is that
with 0, the first read of
+ a request will be made using a short timeout, while with -1, the first
read will be made using the
+ regular socket timeout that is configured on the connector. Setting this
to -2 will cause
+ the connector to not use the poller for keepalive in most situations,
emulating the behavior of
+ the java.io HTTP connector.
+ The default value is -1. Note: on Windows, the actual value of
firstReadTimeout will
+ be 500 + the specified value, if the specified value is strictly
positive.</p>
</attribute>
<attribute name="pollTime" required="false">
<p>Duration of a poll call. Lowering this value will slightly decrease
latency of connections
being kept alive in some cases, but will use more CPU as more poll calls
are being made. The
- default value is 5000 (5ms).</p>
+ default value is 2000 (5ms).</p>
</attribute>
<attribute name="pollerSize" required="false">
<p>Amount of sockets that the poller responsible for polling kept alive
connections can hold at a
- given time. Extra connections will be closed right away. The default
value is 768, corresponding to
- 768 keepalive connections.</p>
+ given time. Extra connections will be closed right away. The default
value is 8192, corresponding to
+ 8192 keepalive connections.</p>
</attribute>
<attribute name="useSendfile" required="false">
@@ -156,7 +162,7 @@
(resulting in a zero length file on the client side). Note that in most
cases, sendfile is a call
that will return right away (being taken care of "synchonously" by the
kernel), and the sendfile
poller will not be used, so the amount of static files which can be sent
concurrently is much larger
- than the specified amount. The default value is 256.</p>
+ than the specified amount. The default value is 1024.</p>
</attribute>
</attributes>
@@ -291,22 +297,28 @@
<attribute name="firstReadTimeout" required="false">
<p>The first read of a request will be made using the specified timeout.
If no data is available
- after the specified time, the socket will be placed in the poller.
Setting this value to 0 will
- increase scalability, but will have a minor impact on latency (see the
related pollTime attribute).
- The default value is 100 (100ms). Note: on Windows, the actual value of
firstReadTimeout will
- be 500 + the specified value.</p>
+ after the specified time, the socket will be placed in the poller. The
value of this attribute is
+ in ms. Setting this value to 0 or -1 will
+ increase scalability by always using a poller to handle keepalive, but
will have a minor impact
+ on latency (see the related pollTime attribute). The difference is that
with 0, the first read of
+ a request will be made using a short timeout, while with -1, the first
read will be made using the
+ regular socket timeout that is configured on the connector. Setting this
to -2 will cause
+ the connector to not use the poller for keepalive in most situations,
emulating the behavior of
+ the java.io HTTP connector.
+ The default value is -1. Note: on Windows, the actual value of
firstReadTimeout will
+ be 500 + the specified value, if the specified value is strictly
positive.</p>
</attribute>
<attribute name="pollTime" required="false">
<p>Duration of a poll call. Lowering this value will slightly decrease
latency of connections
being kept alive in some cases, but will use more CPU as more poll calls
are being made. The
- default value is 5000 (5ms).</p>
+ default value is 2000 (5ms).</p>
</attribute>
<attribute name="pollerSize" required="false">
<p>Amount of sockets that the poller responsible for polling kept alive
connections can hold at a
- given time. Extra connections will be closed right away. The default
value is 768, corresponding to
- 768 keepalive connections.</p>
+ given time. Extra connections will be closed right away. The default
value is 8192, corresponding to
+ 8192 keepalive connections.</p>
</attribute>
</attributes>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
