[HBASE-5250] readAndProcess threw exception java.lang.NullPointerException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Labels: delete
• Assignee: Unassigned
• Reporter: Michael Stack
• Created: 22/Jan/12 22:45
• Updated: 12/Jun/22 20:12
• Resolved: 06/Jan/15 19:11

Description

From Benoit...

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.