commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DBCP-250) maxIdle limit exceeded and number does not decrease
Date Sat, 01 Dec 2007 01:54:43 GMT

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

Phil Steitz commented on DBCP-250:
----------------------------------

Are you using BasicDataSource?  Pls provide configuration information and database and info
on how you are observing the idle connection count.  If you are measuring idle connections
from the database, it is possible that the number of idle connections from the database perspective
will exceed the number of idle connections in the pool.  The number of idle connections that
that pool limits via maxIdle is the number of database connections that are waiting for clients
to check them out of the pool.  When a client application calls getConnection and retrieves
a connection from the pool, the pool does not count this as an idle connection while the client
has it checked out, even if the client is not using it and it is idle from the database engine
perspective.  MaxActive, however, should not be exceeded, so you should not be seeing 18 connections
open from the pool with the default maxActive setting.

testOnIdle does not have to be turned on for excess idle connections to be removed when they
are closed by clients.

> 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.


Mime
View raw message