[
https://issues.apache.org/jira/browse/HBASE-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540938#comment-13540938
]
Jonathan Hsieh commented on HBASE-7459:
---------------------------------------
yup, here's the offending method
{code}
public void shutdown() throws IOException {
spanReceiverHost.closeReceivers();
if (cpHost != null) {
cpHost.preShutdown();
}
if (mxBean != null) {
MBeanUtil.unregisterMBean(mxBean);
mxBean = null;
}
if (this.assignmentManager != null) this.assignmentManager.shutdown();
if (this.serverManager != null) this.serverManager.shutdownCluster();
try {
if (this.clusterStatusTracker != null){
this.clusterStatusTracker.setClusterDown();
}
} catch (KeeperException e) {
LOG.error("ZooKeeper exception trying to set cluster as down in ZK", e);
}
}
{code}
> NPE in HMaster TestlocalHBaseCluster
> ------------------------------------
>
> Key: HBASE-7459
> URL: https://issues.apache.org/jira/browse/HBASE-7459
> Project: HBase
> Issue Type: Bug
> Components: master, test
> Affects Versions: hbase-6055, 0.96.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: hbase-7459.patch
>
>
> TestLocalHBaseCluster has failed intermittently on a unit test run with this
> exception stack.
> {code}
> java.lang.NullPointerException
> at org.apache.hadoop.hbase.master.HMaster.shutdown(HMaster.java:2064)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.shutdown(JVMClusterUtil.java:238)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.shutdown(LocalHBaseCluster.java:430)
> at
> org.apache.hadoop.hbase.TestLocalHBaseCluster.testLocalHBaseCluster(TestLocalHBaseCluster.java:71)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>
> {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
