You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Jiannan Wang (JIRA)" <ji...@apache.org> on 2013/04/05 06:28:16 UTC

[jira] [Updated] (BOOKKEEPER-599) NPE in PerChannelBookieClient

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

Jiannan Wang updated BOOKKEEPER-599:
------------------------------------

    Attachment: BOOKKEEPER-599.patch

Attach a simple fix
                
> NPE in PerChannelBookieClient
> -----------------------------
>
>                 Key: BOOKKEEPER-599
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-599
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-client
>    Affects Versions: 4.2.0, 4.2.1
>            Reporter: Jiannan Wang
>            Assignee: Jiannan Wang
>             Fix For: 4.3.0
>
>         Attachments: BOOKKEEPER-599.patch
>
>
> When log level is DEBUG, a failure read will cause NPE in PerChannelBookieClient (rr.getData() is null):
> {code:java}
> void handleReadResponse(BookieProtocol.ReadResponse rr) {
>     if (LOG.isDebugEnabled()) {
>         LOG.debug("Got response for read request {} entry length: {}",
>                   rr, rr.getData().readableBytes());
>     }
>     ...
> }
> {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