[
https://issues.apache.org/jira/browse/DBCP-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681805#comment-17681805
]
Phil Steitz commented on DBCP-590:
----------------------------------
I will look more at this when I have a little more time, but I suspect this may
be a regression due to the refactoring changes in
344234a758da62aa422f6f67c6e7b1f37329c9c0. IIRC, this functionality used to
work. I would not recommend changing the datasource creation until we
understand what is causing the problem. Could be I am wrong and it did not
work before. I will do some testing and analysis some time this week.
> 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)
