Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 30296 invoked from network); 30 Jan 2007 16:12:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jan 2007 16:12:11 -0000 Received: (qmail 73595 invoked by uid 500); 30 Jan 2007 16:12:02 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 73576 invoked by uid 500); 30 Jan 2007 16:12:02 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 73565 invoked by uid 99); 30 Jan 2007 16:12:02 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jan 2007 08:12:02 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jan 2007 08:11:53 -0800 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1HBva0-0000Hq-C2 for users@tomcat.apache.org; Tue, 30 Jan 2007 08:11:32 -0800 Message-ID: <8709218.post@talk.nabble.com> Date: Tue, 30 Jan 2007 08:11:32 -0800 (PST) From: Henk Fictorie To: users@tomcat.apache.org Subject: Re: mod_jk - connection_pool_size and connection_pool_minsize In-Reply-To: <45BF3F79.9080208@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: henk.fictorie@kpn.com References: <8708555.post@talk.nabble.com> <45BF3F79.9080208@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Mladen Turk wrote: > > Henk Fictorie wrote: >> From reading the documentation I understand that connection_pool_size is >> set >> to its default value, the ThreadsPerChild setting from Apache. >> According to the documentation the connection_pool_minsize is only used >> when >> the connection_pool_size is specified. Since I didn't specify the >> connection_pool_size, I conclude that the connection_pool_minsize is not >> used. But how does it work then? Is there no minimum size for the >> connection >> pool and will all connections be freed (after the connection_pool_timeout >> value)? Or will connections never be freed? >> > > default > connection_pool_minsize = (connection_pool_size + 1) / 2 > Since default connection_pool_size is ThreadsPerChild > the connection_pool_minsize is ThreadsPerChild/2 > So, when you set the connection_pool_timeout without > specifying anything else it would behave like > > worker.xxx.connection_pool_size=ThreadsPerChild > worker.xxx.connection_pool_minsize=ThreadsPerChild/2 > > Regards, > Mladen. > Thanks for the clarification. The documentation for connection_pool_minsize however creates confusing (for me at least). The sentence This property is used only when the connection_pool_size is specified. could be removed from the documentation as it does not give any help. regards Henk Fictorie -- View this message in context: http://www.nabble.com/mod_jk---connection_pool_size-and-connection_pool_minsize-tf3142104.html#a8709218 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org