hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "cuijianwei (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-7684) NullPointerException in SecureClient when Call is cleaned up due to RPC timeout
Date Sun, 27 Jan 2013 09:13:13 GMT

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

cuijianwei updated HBASE-7684:
------------------------------

    Attachment: check_call_null_before_set_in_secure_client.diff
    
> 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
>         Attachments: check_call_null_before_set_in_secure_client.diff
>
>
> 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

Mime
View raw message