Doesn't the db pooling config use a param called something like initSize or
initialSize if you want it to start at that size.
On Nov 6, 2010 2:17 PM, "Christopher Schultz" <ch...@christopherschultz.net>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jim,
>
> On 11/6/2010 2:17 PM, Jim Riggs wrote:
>> On Nov 6, 2010, at 12:50 AM, rujin raj wrote:
>>
>>> Now my server.xml file is like this.As you told i added
>>> executor="tomcatThreradPool" as follows
>>>
>>> <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
>>> maxThreads="1000" minSpareThreads="150"/>
>>>
>>> <Connector port="8080" protocol="HTTP/1.1"
>>> connectionTimeout="20000"
>>> executor="tomcatThreadPool"
>>> maxThreads="1000"
>>> enableLookups="false" disableUploadTimeout="true"
>>> redirectPort="8443" />
>>> Still the minSpareThreads is not taken into account.
>>
>> I believe (if I heard it correctly), either Mark T. or Tim F.
>> explained at ApacheCon this week that the minimum is not immediate.
>> It needs to build up to that level. So, when you start Tomcat, you
>> won't immediately fire up 150 threads for the executor pool, but once
>> >= 150 threads are created in the process of serving requests, it
>> will always keep a minimum of 150 for you.
>
> If that's the case, I find that surprising. I always like to avoid
> violating the principle of least surprise. minSpareThreads as a name
> implies to me that those spares are /always/ available, even immediately
> after startup.
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkzVqbMACgkQ9CaO5/Lv0PBQDACfXZ/jMJ36alpSpvdeQ6tP74OE
> lbsAn2dprnNsvi6F9F44naTySCH3y5+w
> =DpHr
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
