[
https://issues.apache.org/jira/browse/BOOKKEEPER-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442519#comment-13442519
]
Ivan Kelly commented on BOOKKEEPER-383:
---------------------------------------
i've seen the same in TestProtoVersions & BookieClientTest. TestProtoVersions
uses BookieClientTest. I don't think they can be fixed in the same manner, as
BookieClientTest needs to start the bookie server to listen on connections. One
option is to never start GC if zk is null.
> NPE in BookieJournalTest
> ------------------------
>
> Key: BOOKKEEPER-383
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-383
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.1.0
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Priority: Minor
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-383.diff
>
>
> Running org.apache.bookkeeper.bookie.BookieJournalTest
> Exception in thread "GarbageCollectorThread" java.lang.NullPointerException
> at
> org.apache.bookkeeper.meta.AbstractZkLedgerManager.asyncGetLedgersInSingleNode(AbstractZkLedgerManager.java:191)
> at
> org.apache.bookkeeper.meta.AbstractZkLedgerManager.getLedgersInSingleNode(AbstractZkLedgerManager.java:268)
> at
> org.apache.bookkeeper.meta.FlatLedgerManager.garbageCollectLedgers(FlatLedgerManager.java:144)
> at
> org.apache.bookkeeper.bookie.GarbageCollectorThread.doGcLedgers(GarbageCollectorThread.java:226)
> The exception is found in
> https://builds.apache.org/job/bookkeeper-trunk/671/console
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
