You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by re...@apache.org on 2007/04/19 04:18:34 UTC
svn commit: r530233 - in /tomcat/tc6.0.x/trunk/webapps/docs: apr.xml
config/ajp.xml config/http.xml
Author: remm
Date: Wed Apr 18 19:18:33 2007
New Revision: 530233
URL: http://svn.apache.org/viewvc?view=rev&rev=530233
Log:
- Remove some attributes.
Modified:
tomcat/tc6.0.x/trunk/webapps/docs/apr.xml
tomcat/tc6.0.x/trunk/webapps/docs/config/ajp.xml
tomcat/tc6.0.x/trunk/webapps/docs/config/http.xml
Modified: tomcat/tc6.0.x/trunk/webapps/docs/apr.xml
URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/apr.xml?view=diff&rev=530233&r1=530232&r2=530233
==============================================================================
--- tomcat/tc6.0.x/trunk/webapps/docs/apr.xml (original)
+++ tomcat/tc6.0.x/trunk/webapps/docs/apr.xml Wed Apr 18 19:18:33 2007
@@ -145,20 +145,6 @@
<attributes>
- <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. 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
@@ -314,20 +300,6 @@
<attributes>
- <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. 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
Modified: tomcat/tc6.0.x/trunk/webapps/docs/config/ajp.xml
URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/config/ajp.xml?view=diff&rev=530233&r1=530232&r2=530233
==============================================================================
--- tomcat/tc6.0.x/trunk/webapps/docs/config/ajp.xml (original)
+++ tomcat/tc6.0.x/trunk/webapps/docs/config/ajp.xml Wed Apr 18 19:18:33 2007
@@ -235,44 +235,13 @@
connectionTimeout.</p>
</attribute>
- <attribute name="minProcessors" required="false">
- <strong>deprecated</strong>
- <p>The minimum number of processors to start at initialization time.
- If not specified, this atttribute is set to 5.</p>
- </attribute>
-
- <attribute name="maxProcessors" required="false">
- <strong>deprecated</strong>
- <p>The maximum number of processors allowed. This should be
- set to a value that is greater than or equal to the maximum number
- of concurrent connections the remote web server can open to Tomcat
- simultaneously. For example, if the web server is Apache 1.x or 2.x
- Tomcat's <code>maxProcessors</code> should be set to the
- value of Apache's <code>maxClients</code> directive.</p>
- <p>A <code>maxProcessors</code> value of zero (0) signifies that
- the number of processors is unlimited. If not specified, this
- atttribute defaults to 20.</p>
- </attribute>
-
- <attribute name="maxSpareThreads" required="false">
- <p>The maximum number of unused request processing threads that
- will be allowed to exist until the thread pool starts stopping the
- unnecessary threads. The default value is 50.</p>
- </attribute>
-
<attribute name="maxThreads" required="false">
<p>The maximum number of request processing threads to be created
by this <strong>Connector</strong>, which therefore determines the
maximum number of simultaneous requests that can be handled. If
- not specified, this attribute is set to 200.</p>
- </attribute>
-
- <attribute name="minSpareThreads" required="false">
- <p>The number of request processing threads that will be created
- when this <strong>Connector</strong> is first started. The connector
- will also make sure it has the specified number of idle processing
- threads available. This attribute should be set to a value smaller
- than that set for <code>maxThreads</code>. The default value is 4.</p>
+ not specified, this attribute is set to 40. If an executor is associated
+ with this connector, this attribute is ignored as the connector will
+ execute tasks using the executor rather than an internal thread pool.</p>
</attribute>
<attribute name="port" required="true">
Modified: tomcat/tc6.0.x/trunk/webapps/docs/config/http.xml
URL: http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/webapps/docs/config/http.xml?view=diff&rev=530233&r1=530232&r2=530233
==============================================================================
--- tomcat/tc6.0.x/trunk/webapps/docs/config/http.xml (original)
+++ tomcat/tc6.0.x/trunk/webapps/docs/config/http.xml Wed Apr 18 19:18:33 2007
@@ -310,25 +310,13 @@
If not specified, this attribute is set to 100.</p>
</attribute>
- <attribute name="maxSpareThreads" required="false">
- <p>The maximum number of unused request processing threads that
- will be allowed to exist until the thread pool starts stopping the
- unnecessary threads. The default value is 50.</p>
- </attribute>
-
<attribute name="maxThreads" required="false">
<p>The maximum number of request processing threads to be created
by this <strong>Connector</strong>, which therefore determines the
maximum number of simultaneous requests that can be handled. If
- not specified, this attribute is set to 200.</p>
- </attribute>
-
- <attribute name="minSpareThreads" required="false">
- <p>The number of request processing threads that will be created
- when this <strong>Connector</strong> is first started. The connector
- will also make sure it has the specified number of idle processing
- threads available. This attribute should be set to a value smaller
- than that set for <code>maxThreads</code>. The default value is 4.</p>
+ not specified, this attribute is set to 40. If an executor is associated
+ with this connector, this attribute is ignored as the connector will
+ execute tasks using the executor rather than an internal thread pool.</p>
</attribute>
<attribute name="noCompressionUserAgents" required="false">
@@ -366,16 +354,6 @@
By default, a buffers of 9000 bytes will be used.</p>
</attribute>
- <attribute name="strategy" required="false">
- <p>The thread pooling strategy which will be used. The default strategy does
- not use a master thread, but a more conventional strategy using a
- master listener thread can be used by setting "ms" as this attribute's value.
- The master strategy will work significantly better using the threadPriority
- attribute, which will apply only to the thread which listens on the server socket.
- This is set to <code>lf</code> by default.
- </p>
- </attribute>
-
<attribute name="tcpNoDelay" required="false">
<p>If set to <code>true</code>, the TCP_NO_DELAY option will be
set on the server socket, which improves performance under most
@@ -724,7 +702,7 @@
Read HTTP Request Blocking Non Blocking Blocking
Read HTTP Body Blocking Blocking Blocking
Write HTTP Response Blocking Blocking Blocking
- SSL Support Java SSL Java SSL Open SSL
+ SSL Support Java SSL Java SSL OpenSSL
SSL Handshake Blocking Non blocking Blocking
Max Connections maxThreads See polling size See polling size
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org