commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Communier (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (POOL-267) Use of AbandonListener instead of PrintWriter when a pool object is detected in an abandon state
Date Fri, 18 Jul 2014 21:06:05 GMT

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

Anthony Communier edited comment on POOL-267 at 7/18/14 9:05 PM:
-----------------------------------------------------------------

You will find attached a patch with an implementation of AbandonedListener (with UnitTest)

I have added some getter on PoolObject in order to get stack traces (borrow & usage)




was (Author: anthonyc):
You will find attachjed a patch with an implementation of AbandonedListener with UnitTest

I have added some getter on PoolObject in order to get stack traces (borrow & usage)



> 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)

Mime
View raw message