[
https://issues.apache.org/jira/browse/DBCP-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547384
]
Wes Clark commented on DBCP-250:
--------------------------------
The behavior you describe is the behavior I expected. We are getting
connections from the JDBC driver and adding them to the pool. We are not using
the BasicDataSource (although I wish we did). We configure the application the
JDBC connection string, and pass it to the vendor's driver.
Does the proper behavior of the connection pool depend upon the use of a
BasicDataSource?
> 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.
