Return-Path: X-Original-To: apmail-commons-user-archive@www.apache.org Delivered-To: apmail-commons-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 349D61753F for ; Sat, 18 Oct 2014 00:38:55 +0000 (UTC) Received: (qmail 44998 invoked by uid 500); 18 Oct 2014 00:38:54 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 44878 invoked by uid 500); 18 Oct 2014 00:38:54 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 44867 invoked by uid 99); 18 Oct 2014 00:38:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Oct 2014 00:38:53 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of abiacco@handll.com does not designate 209.85.217.182 as permitted sender) Received: from [209.85.217.182] (HELO mail-lb0-f182.google.com) (209.85.217.182) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Oct 2014 00:38:48 +0000 Received: by mail-lb0-f182.google.com with SMTP id z11so1491296lbi.27 for ; Fri, 17 Oct 2014 17:38:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=ghBXgRN1d7kIZEyYityanFfkzK64/9HXqMax+ogfRfs=; b=iXATEwuSlfEBkVbnyRiPWaNtTKWHEUGllwX3eFSA5YbheMl/LwPiARHntz389qIdxO fLIgjcmlpqtHevz/q4x5tq2IT/OUtLXhxB1h9B8bi6BJYWMVyN7rjY1MNznVwFjWGKv6 jw2GOfyCfmvk92OTMJIogMt0dcvKlY47ogyJ3/SKycyfc4b98UNsVZIzo2FlZSJ9OghA hjMzN3YJ+DgPzkTZx+apXWGrsj/Z83TXuUk0uSqOaGSsimWjzTPgZlmvRebsYrhNT+n/ 3+P39ahDixwmt0FSMxIPjCkVdXKnikWy4UnESTIKSrJlZJ1FU/KzSVcBdkpY9I/Dof++ ihsQ== X-Gm-Message-State: ALoCoQleDeVS3W+x+cojIGdhtBsI03wUYpQwoNOv/pxH66Mn8gD4BTkIM2DcumewDVYCyed/nze2 MIME-Version: 1.0 X-Received: by 10.112.24.161 with SMTP id v1mr12494733lbf.36.1413592706640; Fri, 17 Oct 2014 17:38:26 -0700 (PDT) Received: by 10.25.25.196 with HTTP; Fri, 17 Oct 2014 17:38:26 -0700 (PDT) Date: Fri, 17 Oct 2014 18:38:26 -0600 Message-ID: Subject: evictor destroying connections below minIdle? From: Anthony Biacco To: user@commons.apache.org Content-Type: multipart/alternative; boundary=001a11347b8e2302340505a7b3fd X-Virus-Checked: Checked by ClamAV on apache.org --001a11347b8e2302340505a7b3fd Content-Type: text/plain; charset=UTF-8 I just started running pool 2.2 alongside dbcp 2.0.1 in tomcat 7 against mysql. I noticed a situation while running the idle evictor where there's a time during eviction where the number of connections drops below the value set for minIdle, so in theory if all connections were idle for minEvictableIdleTimeMillis, i could have no free connections. After the eviction, connections seem to be created back up to minIdle. I expected it to only evict down to the minIdle value, not evict all eligible idle connections and then recreate up to minIdle. The way i'm viewing the number of connections is through mysql's "show full processlist" command. Is what i'm describing possible or am I missing something? If it is possible, couldn't this cause the resource to become unavailable in the time between destruction and recreation? Here's my config: initialSize="15" minIdle="15" maxIdle="100" maxTotal="200" maxWaitMillis="4000" defaultQueryTimeout="20" testOnBorrow="true" testWhileIdle="true" blockWhenExhausted="true" numTestsPerEvictionRun="50" timeBetweenEvictionRunsMillis="120000" minEvictableIdleTimeMillis="119000" validationQuery="SELECT 1" validationQueryTimeout="2" removeAbandoned="true" removeAbandonedOnBorrow="true" removeAbandonedTimeout="60" logAbandoned="true" Thanks, -Tony --001a11347b8e2302340505a7b3fd--