commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anthony Biacco <abia...@handll.com>
Subject Re: [pool] [dbcp] Re: evictor destroying connections below minIdle?
Date Sat, 18 Oct 2014 17:47:43 GMT
On Oct 18, 2014 9:46 AM, "Phil Steitz" <phil.steitz@gmail.com> wrote:
>
> On 10/17/14 5:38 PM, Anthony Biacco wrote:

> Yes, this is possible.  When evicting idle instances due to
> minEvictableIdleTimeMillis exceeded, the evictor does not take into
> account the number of idle instances remaining in the pool and it
> performs the evict, ensure min idle actions in sequence.  If you
> want to avoid the destroy / recreate scenario, you can use
> softMinEvictableIdleTimeMillis instead.

Ok thanks, I'll try using that.

> > If it is possible, couldn't this cause the resource to become
unavailable
> > in the time between destruction and recreation?
>
> I am not sure what you mean here.  This could lead to the idle
> instance count hitting zero, but client threads will still get
> served as long as maxTotal is not exceeded.

Sorry, you're right, don't know what I was thinking. More beer!

Thanks for the help.

-Tony

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message