[
https://issues.apache.org/jira/browse/POOL-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722585#comment-13722585
]
Mark Thomas commented on POOL-236:
----------------------------------
Various reasons. For example, if validation fails with an exception when
returning an object, the object still needs to be destroyed so the validation
exception has to be swallowed (POOL uses Java 6). Another case is if the
evictor encounters an exception. Since it is a background thread, there is no
code to handle any exception thrown. For the full list, look for calls to
BaseGenericObjectPool#swallowException().
> Replace JMX notifications with an event listener
> ------------------------------------------------
>
> Key: POOL-236
> URL: https://issues.apache.org/jira/browse/POOL-236
> Project: Commons Pool
> Issue Type: Bug
> Reporter: Mark Thomas
>
> JMX notifications were chosen as a way to expose swallowed exceptions to the
> user without adding a dependency on a logging framework. In discussions about
> logging for DBCP, James Carman suggested an event listener which is a much
> better solution to POOL's logging problem than JMX notifications.
> Aim to implement this change in time for the 2.0 release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
