[
https://issues.apache.org/jira/browse/DBCP-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793767#comment-17793767
]
Réda Housni Alaoui edited comment on DBCP-590 at 12/6/23 3:03 PM:
------------------------------------------------------------------
{quote}I will do some testing and analysis some time this week.{quote}
[~psteitz], could you take a look at this issue? FYI, my workaround caused
DBCP-593.
was (Author: ralaoui):
{quote}I will do some testing and analysis some time this week.{quote}
[~psteitz], could you take a look at this issue?
> BasicDataSource#setAbandonedUsageTracking has no effect
> -------------------------------------------------------
>
> Key: DBCP-590
> URL: https://issues.apache.org/jira/browse/DBCP-590
> Project: Commons DBCP
> Issue Type: Bug
> Affects Versions: 2.9.0
> Reporter: Réda Housni Alaoui
> Priority: Major
>
> Passing {{true}} to {{BasicDataSource#setAbandonedUsageTracking(boolean
> usageTracking)}} has no effect because {{UsageTracking#use}} is never called.
> From what I found, {{usageTracking}} can only work if the object pool is of
> type {{ProxiedObjectPool}} . Alas, BasicDataSource enforces
> {{GenericObjectPool}} concrete type preventing us from overriding
> {{BasicDataSource#createObjectPool}} to return a {{ProxiedObjectPool}} .
> Is there something I missed or a workaround?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
