commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (POOL-300) Abandoned object stack traces may not be written
Date Thu, 06 Aug 2015 22:57:04 GMT

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

Phil Steitz closed POOL-300.
----------------------------

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

Mime
View raw message