You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/09/11 01:57:52 UTC

[jira] [Resolved] (HBASE-9122) NPE in MasterMonitorCallable.close()

     [ https://issues.apache.org/jira/browse/HBASE-9122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-9122.
--------------------------

    Resolution: Duplicate

Resolving as dup of HBASE-9498 (it has more stack trace detail)
                
> NPE in MasterMonitorCallable.close()
> ------------------------------------
>
>                 Key: HBASE-9122
>                 URL: https://issues.apache.org/jira/browse/HBASE-9122
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.95.1
>            Reporter: Himanshu Vashishtha
>            Priority: Minor
>
> Found this npe while running Integration test suite:
> {code}
> Caused by: java.lang.NullPointerException
> 	at org.apache.hadoop.hbase.client.HBaseAdmin$MasterMonitorCallable.close(HBaseAdmin.java:2691)
> 	at org.apache.hadoop.hbase.client.HBaseAdmin.executeCallable(HBaseAdmin.java:2721)
> 	at org.apache.hadoop.hbase.client.HBaseAdmin.getClusterStatus(HBaseAdmin.java:1949)
> 	at org.apache.hadoop.hbase.util.ChaosMonkey$MoveRegionsOfTable.perform(ChaosMonkey.java:349)
> 	at org.apache.hadoop.hbase.mttr.IntegrationTestMTTR$ActionCallable.call(IntegrationTestMTTR.java:490)
> 	at org.apache.hadoop.hbase.mttr.IntegrationTestMTTR$ActionCallable.call(IntegrationTestMTTR.java:481)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)
> {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