On Nov 6, 2010, at 2:17 PM, Christopher Schultz wrote:
>> 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 thr
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"
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jim,
>
> On 11/6/2010 2:17 PM, Jim Riggs wrote:
>> On Nov 6, 2010
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Connector Setting Problem in tomcat 6.0.29
> 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
-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
>>
>> > maxThreads="1000" minSpareThreads="150"/>
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
>
> maxThreads="1000" minSpareThreads="150"/>
>
> connectionTimeout="2"
> executor="tomcatThreadPool"
> maxThreads="1000"
>
On 06/11/2010 05:50, rujin raj wrote:
> Hi,
>
> Now my server.xml file is like this.As you told i added
> executor="tomcatThreradPool" as follows
>
>maxThreads="1000" minSpareThreads="150"/>
>
> connectionTimeout="2"
> executor="tomcatThreadPool"
> maxThreads="100
