You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Cosmin Lehene (JIRA)" <ji...@apache.org> on 2015/01/06 18:04:35 UTC
[jira] [Commented] (HBASE-5250) readAndProcess threw exception
java.lang.NullPointerException
[ https://issues.apache.org/jira/browse/HBASE-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266401#comment-14266401 ]
Cosmin Lehene commented on HBASE-5250:
--------------------------------------
[~saint.ack@gmail.com], [~apurtell] review/close?
> readAndProcess threw exception java.lang.NullPointerException
> -------------------------------------------------------------
>
> Key: HBASE-5250
> URL: https://issues.apache.org/jira/browse/HBASE-5250
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Labels: delete
>
> From Benoit...
> {code}2012-01-20 17:13:20,634 INFO org.apache.hadoop.ipc.HBaseServer: IPC
> Server Responder: doAsyncWrite threw exception java.io.IOException:
> Broken pipe
> 2012-01-20 17:13:20,635 WARN org.apache.hadoop.ipc.HBaseServer: IPC
> Server listener on 52146: readAndProcess threw exception
> java.lang.NullPointerException. Count of bytes read: 0
> java.lang.NullPointerException
> at org.apache.hadoop.hbase.ipc.HBaseServer$Connection.readAndProcess(HBaseServer.java:1119)
> at org.apache.hadoop.hbase.ipc.HBaseServer$Listener.doRead(HBaseServer.java:703)
> at org.apache.hadoop.hbase.ipc.HBaseServer$Listener$Reader.doRunLoop(HBaseServer.java:495)
> at org.apache.hadoop.hbase.ipc.HBaseServer$Listener$Reader.run(HBaseServer.java:470)
> 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:680)
> This is when I unexpectedly close a connection to a RS. When the
> channel gets disconnected, some buffer is nulled out, but then if
> readAndProcess() is called again, it triggers the NPE above. Not a
> huge deal, but also indicates that maybe some logic in the RS's error
> handling is incorrect.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)