Author: rjung
Date: Fri Oct 3 06:12:11 2008
New Revision: 701371
URL: http://svn.apache.org/viewvc?rev=701371&view=rev
Log:
Enhance description of connection_pool_size in docs.
Modified:
tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml
tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml
tomcat/connectors/trunk/jk/xdocs/reference/workers.xml
Modified: tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml?rev=701371&r1=701370&r2=701371&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml Fri Oct 3
06:12:11 2008
@@ -162,10 +162,15 @@
to use this attribute in combination with Apache httpd. For
Apache httpd we automatically detect the number of threads per
process and set the maximum pool size to this value. For IIS we use
-a default value of 250, for the Sun Web Server the default is "1".
-We recommend adjusting this value for IIS and the Sun Web Server
+a default value of 250 (before version 1.2.20: 10),
+for the Sun Web Server the default is "1".
+We strongly recommend adjusting this value for IIS and the Sun Web Server
to the number of requests one web server process should
-be able to send to a backend in parallel.
+be able to send to a backend in parallel. You should measure how many
connections
+you need during peak hours without performance problems, and then add some
+percentage depending on your growth rate etc. Finally you should check,
+whether your web server processes are able to use at least as many threads,
+as you configured as the pool size.
</p>
<p>
The JK attribute <b>connection_pool_minsize</b> defines,
Modified: tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml?rev=701371&r1=701370&r2=701371&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/miscellaneous/changelog.xml Fri Oct 3
06:12:11 2008
@@ -43,6 +43,9 @@
<br />
<subsection name="Native">
<changelog>
+ <update>
+ Documentation: Enhance description of connection_pool_size. (rjung)
+ </update>
<fix>
IIS: SERVER_NAME variable can be the same for
multiple different server instances if requests
Modified: tomcat/connectors/trunk/jk/xdocs/reference/workers.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/reference/workers.xml?rev=701371&r1=701370&r2=701371&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/reference/workers.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/reference/workers.xml Fri Oct 3 06:12:11
2008
@@ -310,12 +310,21 @@
process can made.
<p>
Connection pool size property is only used for multi threaded
-web servers such as Apache 2.0 (worker), IIS and Netscape. The
connection_pool_size property
-should reflect the number of threads per child process. JK will discover
-the number of threads per child process on Apache 2 web server with worker-mpm
and set
-its default value to match the ThreadsPerChild Apache directive. For IIS the
default
-value is 250. For other web servers than Apache or IIS the default value is 1
-and you should adjust it manually.
+web servers such as Apache, IIS and Netscape/Sun. The connection_pool_size
property
+needs to reflect the number of requests one web server process should
+be able to send to a backend in parallel. Usually this is the same as
+the number of threads per web server process. JK will discover
+this number for the Apache web server automatically and set the pool size to
+this value. For IIS the default value is 250 (before version 1.2.20: 10),
+for Netscape/Sun the default value is 1.
+</p>
+<p>We strongly recommend adjusting this value for IIS and the Netscape/Sun
+to the number of requests one web server process should
+be able to send to a backend in parallel. You should measure how many
connections
+you need during peak activity without performance problems, and then add some
+percentage depending on your growth rate. Finally you should check,
+whether your web server processes are able to use at least as many threads,
+as you configured as the pool size.
</p>
<warn>Do not use connection_pool_size with values higher then 1 on <b>Apache
2.x prefork</b> or <b>Apache 1.3.x</b>!</warn>
</directive>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
