[ https://issues.apache.org/jira/browse/DBCP-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz resolved DBCP-590. ------------------------------ Fix Version/s: 2.11.1 Resolution: Fixed I am really sorry it took me so long to figure this out. It looks like indeed this has been broken since 2.0 and [~ralaoui] is right that the root cause was BDS not calling use() on the PoolableConnections. I added a test to confirm that it is working now (as of 4dd9df42ffe0905c6fd74515017a22505ae863cf). > 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 > Fix For: 2.11.1 > > > 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)