You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2014/02/05 21:34:09 UTC
[jira] [Commented] (DBCP-388) Support AbandonedConfig in
SharedPoolDataSource
[ https://issues.apache.org/jira/browse/DBCP-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892533#comment-13892533 ]
Mark Thomas commented on DBCP-388:
----------------------------------
SharedPoolDataSource is based on GenericKeyedObjectPool which itself does not support AbandonedConfig. There would therefore need to be changes in Commons Pool to support this. I took a quick look - I don't think it is impossible but it is non-trivial.
> Support AbandonedConfig in SharedPoolDataSource
> -----------------------------------------------
>
> Key: DBCP-388
> URL: https://issues.apache.org/jira/browse/DBCP-388
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.4
> Environment: Linux and Java 1.6
> Reporter: Michael Kerr
> Priority: Minor
> Labels: features
>
> BasicDataSource has support for AbandonedConfig
> SharedPoolDataSource does not currently support reclaiming abandoned connections.
> It would be helpful if the user can extend the underlying connection pool to add features like abandoned connection management. This is possible with BasicDataSource.
> Currently the only solution is to extend classes or replace classes in the Apache package namespace.
> Thanks for looking,
> Michael
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)