From: Jeff Trawick Date: Sun, 19 Dec 2010 22:47:04 +0000 (+0000) Subject: generated doc changes X-Git-Tag: 2.2.18~231 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f4672dda920a029cc5335c72eef60618d768dcf8;p=thirdparty%2Fapache%2Fhttpd.git generated doc changes git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1050959 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index 9eea1b056bf..c502a5d9092 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -916,23 +916,30 @@ through -

As of Apache 2.1, the ability to use pooled connections to a backend - server is available. Using the key=value parameters it is - possible to tune this connection pooling. The default for a Hard - Maximum for the number of connections is the number of threads per - process in the active MPM. In the Prefork MPM, this is always 1, while with - the Worker MPM it is controlled by the - ThreadsPerChild.

- -

Setting min will determine how many connections will always - be open to the backend server. Upto the Soft Maximum or smax - number of connections will be created on demand. Any connections above - smax are subject to a time to live or ttl. Apache - will never create more than the Hard Maximum or max connections - to the backend server.

+

In Apache HTTP Server 2.1 and later, mod_proxy supports pooled + connections to a backend server. Connections created on demand + can be retained in a pool for future use. Limits on the pool size + and other settings can be coded on + the ProxyPass directive + using key=value parameters, described in the table + below.

+ +

By default, mod_proxy will allow and retain the maximum number of + connections that could be used simultaneously by that web server child + process. Use the max parameter to reduce the number from + the default. Use the ttl parameter to set an optional + time to live; connections which have been unused for at least + ttl seconds will be closed. ttl can be used + to avoid using a connection which is subject to closing because of the + backend server's keep-alive timeout.

+ +

The pool of connections is maintained per web server child + process, and max and other settings are not coordinated + among all child processes, except when only one child process is allowed + by configuration or MPM design.

-

- ProxyPass /example http://backend.example.com smax=5 max=20 ttl=120 retry=300 +

Example

+ ProxyPass /example http://backend.example.com max=20 ttl=120 retry=300

@@ -941,23 +948,27 @@ through - + - + - + -
Description
min 0Minimum number of connections that will always - be open to the backend server.
Minimum number of connection pool entries, unrelated to the + actual number of connections. This only needs to be modified from the + default for special circumstances where heap memory associated with the + backend connections should be preallocated or retained.
max 1...nHard Maximum number of connections that will be - allowed to the backend server. The default for a Hard Maximum - for the number of connections is the number of threads per process in the - active MPM. In the Prefork MPM, this is always 1, while with the Worker MPM - it is controlled by the ThreadsPerChild. - Apache will never create more than the Hard Maximum connections - to the backend server.
Maximum number of connections that will be allowed to the + backend server. The default for this limit is the number of threads + per process in the active MPM. In the Prefork MPM, this is always 1, + while with other MPMs it is controlled by the + ThreadsPerChild directive.
smax maxUpto the Soft Maximum - number of connections will be created on demand. Any connections above - smax are subject to a time to live or ttl. -
Retained connection pool entries above this limit are freed + during certain operations if they have been unused for longer than + the time to live, controlled by the ttl parameter. If + the connection pool entry has an associated connection, it will be + closed. This only needs to be modified from the default for special + circumstances where connection pool entries and any associated + connections which have exceeded the time to live need to be freed or + closed more aggressively.
acquire - If set this will be the maximum time to wait for a free @@ -1076,9 +1087,9 @@ through
ttl -Time To Live for the inactive connections above the - smax connections in seconds. Apache will close all - connections that has not been used inside that time period. + Time to live for inactive connections and associated connection + pool entries, in seconds. Those which are unused for at least + ttl seconds will be destroyed.
diff --git a/docs/manual/mod/mod_proxy.xml.ja b/docs/manual/mod/mod_proxy.xml.ja index fa925eb8b2e..6e9b45c06f3 100644 --- a/docs/manual/mod/mod_proxy.xml.ja +++ b/docs/manual/mod/mod_proxy.xml.ja @@ -1,7 +1,7 @@ - +