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

Posted to issues@commons.apache.org by "Phil Steitz (JIRA)" <ji...@apache.org> on 2015/07/27 22:24:04 UTC

[jira] [Resolved] (POOL-300) Abandoned object stack traces may not be written

     [ https://issues.apache.org/jira/browse/POOL-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phil Steitz resolved POOL-300.
------------------------------
    Resolution: Fixed

Flush added to DefaultPooledObject printStackTrace in r1692943.

> Abandoned object stack traces may not be written
> ------------------------------------------------
>
>                 Key: POOL-300
>                 URL: https://issues.apache.org/jira/browse/POOL-300
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4.1
>            Reporter: Phil Steitz
>             Fix For: 2.4.2
>
>
> When writing stack traces for abandoned object tracking, DefaultPooledObject does not flush the Printwriter.  The default Printwriter in AbandonedConfig is System.out without autoflush enabled.  This means that stack traces may not be effectively logged (if there is just one, for example).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)