[
https://issues.apache.org/jira/browse/BOOKKEEPER-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624996#comment-13624996
]
Hudson commented on BOOKKEEPER-599:
-----------------------------------
Integrated in bookkeeper-trunk #168 (See
[https://builds.apache.org/job/bookkeeper-trunk/168/])
BOOKKEEPER-599: NPE in PerChannelBookieClient (jiannan via sijie) (Revision
1465437)
Result = SUCCESS
sijie :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/PerChannelBookieClient.java
> 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, 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
