[
https://issues.apache.org/jira/browse/POOL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved POOL-142.
------------------------------
Resolution: Duplicate
Agree with the analysis. Logging the exception is probably the best approach.
See POOL-131.
> Swallowing exceptions throw by factory destroy() methods can hide genuine
> issues
> --------------------------------------------------------------------------------
>
> Key: POOL-142
> URL: https://issues.apache.org/jira/browse/POOL-142
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Mark Thomas
> Fix For: 2.0
>
>
> Swallowing all factory exceptions prevents the factory indicating to the pool
> that there is an issue. For example, attempting to destroy an object twice
> may indicate a bug in the pool code. The factory exception policy needs to be
> reviewed. If changed this will be an API change to needs to wait until 2.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
