You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2018/06/18 22:34:00 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=16516427#comment-16516427 ]
Gary Gregory commented on DBCP-388:
-----------------------------------
I propose we close this since we changed DBCP in 2.x with AbandonedTrace only being subclassed by our delegates for connections, statements, and result set.
> 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
> Fix For: 2.4.1
>
>
> 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
(v7.6.3#76005)