Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <7249875.1196709703067.JavaMail.jira@brutus>
Date: Mon, 3 Dec 2007 11:21:43 -0800 (PST)
From: "Wes Clark (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (DBCP-250) maxIdle limit exceeded and number does
 not decrease
In-Reply-To: <3334322.1196312143437.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DBCP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547951 ] 

Wes Clark commented on DBCP-250:
--------------------------------

I hope to be investigating this behavior in more detail at a later date.    We also plan to make testOnIdle the default behavior, which seems to fix the problem.

> maxIdle limit exceeded and number does not decrease
> ---------------------------------------------------
>
>                 Key: DBCP-250
>                 URL: https://issues.apache.org/jira/browse/DBCP-250
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Wes Clark
>
> Today, during load testing we noticed that the number of idle database connections exceeded the default value. The default values for maxIdle and maxActive are being used. After running the application with 200 users, the number of idle connection went to 18 and stayed there. 
> Is this a bug?  Does testOnIdle need to be set to true for the idle connections to be decreased?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.