commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Cameron (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DBCP-373) Ability to configure upper bound on total number of connections managed by pooled data sources across all keys (user/password).
Date Sun, 11 Dec 2011 07:21:40 GMT
Ability to configure upper bound on total number of connections managed by pooled data sources
across all keys (user/password).
-------------------------------------------------------------------------------------------------------------------------------

                 Key: DBCP-373
                 URL: https://issues.apache.org/jira/browse/DBCP-373
             Project: Commons Dbcp
          Issue Type: Improvement
    Affects Versions: 1.4
            Reporter: Scott Cameron


For a discussion about this request, please refer to: http://www.mail-archive.com/user@commons.apache.org/msg07215.html.

In general, it feels like SharedPoolDataSource and PerUserPoolDataSource could be made much
more powerful and flexible by exposing as much of the configurability of the underlying ObjectPool
as possible.  It seems to me that if consumers are going to want to customize behavior it
is very likely that it is the ObjectPool that they will want to tweak.  Exposing the power
of the inner pool would be really useful.

But if that doesn't make sense, at least allowing a global cap on the total number of connections
across all keys in the pool data source would solve at least the problem I describe in the
mailing list post.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message