You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Flavio Junqueira (JIRA)" <ji...@apache.org> on 2015/08/06 22:58:06 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14660779#comment-14660779 ]
Flavio Junqueira commented on BOOKKEEPER-863:
---------------------------------------------
hi [~tedyu], I think you're right, we should be calling close on the ledger manager instances, is that what you're suggesting? feel free to assign it to yourself if are interested in contributing a patch.
> 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
>
> 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)