On Thu, Feb 1, 2018 at 1:02 PM, Mark Thomas <ma...@apache.org> wrote:
> On 01/02/18 20:57, Pawel Veselov wrote:
>> Hello.
>>
>> It looks like in tomcat 8 (looking at master's HEAD), the minIdle
>> support is broken. According to docs, minIdle supposed to do : "The
>> minimum number of established connections that should be kept in the
>> pool at all times. The connection pool can shrink below this number if
>> validation queries fail."
>>
>> I see that pool cleaner thread checks if the minIdle is *less* than
>> pool size, and only then invokes checkIdle(). checkIdle() then will
>> remove(!) connections from idle pool until the value drops down to
>> minIdle. But I don't see any code that will add connections when
>> minIdle is not met, and the documentation suggests that that's the
>> intent.
>>
>> Am I misunderstanding something? Is there a way to keep a level of
>> connections in the pool? I don't want to have initialSize control
>> that, as I need to at 0, to prevent failures during pool
>> initialization...
> But that is what initial size is for.

Indisputably so. However, that would be the only other way to achieve
this, as long as the database connection don't die.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to