You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2014/08/19 10:53:19 UTC

[jira] [Commented] (POOL-267) Use of AbandonListener instead of PrintWriter when a pool object is detected in an abandon state

    [ https://issues.apache.org/jira/browse/POOL-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102035#comment-14102035 ] 

Mark Thomas commented on POOL-267:
----------------------------------

Just something to think about. We might want to make the listener more generic in case there are other events we want to raise in the future.

> Use of AbandonListener instead of PrintWriter when a pool object is detected in an abandon state
> ------------------------------------------------------------------------------------------------
>
>                 Key: POOL-267
>                 URL: https://issues.apache.org/jira/browse/POOL-267
>             Project: Commons Pool
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Anthony Communier
>         Attachments: AbandonedListenerPatch.diff
>
>
> I would be great to have a more flexible mecanism for abandon detection. Having just a PrintWriter is too restrictive. With an AbandonListener it would be possible to make more things like using log API or enabling supervision of application.



--
This message was sent by Atlassian JIRA
(v6.2#6252)