You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/01/14 17:14:13 UTC
[jira] [Updated] (BOOKKEEPER-285) TestZkSubscriptionManager quits
due to NPE, so other tests are not run in hedwig server.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Kelly updated BOOKKEEPER-285:
----------------------------------
Fix Version/s: (was: 4.2.0)
> TestZkSubscriptionManager quits due to NPE, so other tests are not run in hedwig server.
> ----------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-285
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-285
> Project: Bookkeeper
> Issue Type: Bug
> Components: hedwig-server
> Affects Versions: 4.1.0
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.1.0
>
> Attachments: BOOKKEEPER-285.diff
>
>
> {code}
> 2012-06-05 01:33:46,366 - ERROR - [main-EventThread:TerminateJVMExceptionHandler@28] - Uncaught exception in thread main-EventThread
> java.lang.NullPointerException
> at org.apache.hedwig.server.subscriptions.AbstractSubscriptionManager.updateMessageBound(AbstractSubscriptionManager.java:457)
> at org.apache.hedwig.server.subscriptions.AbstractSubscriptionManager$AcquireOp$1.operationFinished(AbstractSubscriptionManager.java:207)
> at org.apache.hedwig.server.subscriptions.AbstractSubscriptionManager$AcquireOp$1.operationFinished(AbstractSubscriptionManager.java:157)
> at org.apache.hedwig.server.meta.ZkMetadataManager$7.safeProcessResult(ZkMetadataManager.java:352)
> at org.apache.hedwig.zookeeper.SafeAsyncZKCallback$ChildrenCallback.processResult(SafeAsyncZKCallback.java:66)
> at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:594)
> at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:497)
> {code}
--
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