commons-issues mailing list archives

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


Phil Steitz commented on DBCP-250:

You do not need to use BasicDataSource.   If you have overriden PoolalbleConnectionFactory.makeObject
and you are not returning / using PoolableConnections, then it is possible that you are not
properly closing connections. If you think you have discovered a bug in one of the DBCP classes,
we can investigate it here if you provide code and ideally a failing test case.  If what you
are looking for is help on how to use the classes, it would be better to close this issue
and ask questions on the commons user list.  (

> maxIdle limit exceeded and number does not decrease
> ---------------------------------------------------
>                 Key: DBCP-250
>                 URL:
>             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

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

View raw message