You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "cuijianwei (JIRA)" <ji...@apache.org> on 2013/01/27 10:07:17 UTC

[jira] [Created] (HBASE-7684) NullPointerException in SecureClient when Call is cleaned up due to RPC timeout

cuijianwei created HBASE-7684:
---------------------------------

             Summary: NullPointerException in SecureClient when Call is cleaned up due to RPC  timeout
                 Key: HBASE-7684
                 URL: https://issues.apache.org/jira/browse/HBASE-7684
             Project: HBase
          Issue Type: Bug
          Components: security
    Affects Versions: 0.94.3
            Reporter: cuijianwei


We find NullPointException when using SecureClient to access hbase. From the source code, we find that receiveResponse() will not check call != null before invoke call.setValue(...)(line 378 and 380 in SecureClient.java). However, as explained in receiveResponse() of HBaseClient, the call may have been cleaned up due to RPC timeout; therefore, it should be better to check call != null before invoke call.setValue(...) in SecureClient

--
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