You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2003/08/26 15:29:33 UTC

DO NOT REPLY [Bug 18012] - BasicDataSource doesn't include PreparedStmt Pooling

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18012>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18012

BasicDataSource doesn't include PreparedStmt Pooling





------- Additional Comments From dirk.verbeeck@pandora.be  2003-08-26 13:29 -------
The problem with the submitted patch is that the maxActive & maxIdle parameters
of the GenericKeyedObjectPool are caps on the pool PER KEY!

The DBCP component creates for each PoolingConnection a GenericKeyedObjectPool.
The key is the sql string and the object is the actual PoolablePreparedStatement.

If a database has a maximum number of open statements then the limit is on the
total number of open statements on the connection.

Extra functionality is needed in GenericKeyedObjectPool to implement this feature.