You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Matteo Merli (JIRA)" <ji...@apache.org> on 2016/05/16 21:48:16 UTC
[jira] [Closed] (BOOKKEEPER-863) Potential resource leak with
unclosed LedgerManager in BookieShell
[ https://issues.apache.org/jira/browse/BOOKKEEPER-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matteo Merli closed BOOKKEEPER-863.
-----------------------------------
Closed as part of BookKeeper-4.4.0 release
> Potential resource leak with unclosed LedgerManager in BookieShell
> ------------------------------------------------------------------
>
> Key: BOOKKEEPER-863
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-863
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 4.4.0
>
> Attachments: bookkeeper-863-v2.patch, bookkeeper-863-v2.patch, bookkeeper-863.patch
>
>
> There're more than one occurrence.
> Here is an example in ListLedgersCmd#runCmd():
> {code}
> LedgerManagerFactory mFactory = LedgerManagerFactory.newLedgerManagerFactory(bkConf, zk);
> LedgerManager m = mFactory.newLedgerManager();
> {code}
> m is not closed upon leaving the method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)