Filed, https://issues.apache.org/jira/browse/HBASE-4980 . Will submit a patch tomorrow.
On Wed, Dec 7, 2011 at 7:52 PM, Shrijeet Paliwal <[email protected]>wrote: > Is line #583 in your HBaseClient line #14 in your pastebin? (When I >> look at 0.90.3 tag, line #583 takes me someplace unrelated: > > > Yes you are right 583 == 14 . Like I mentioned, I am running a patched > version of 0.90.3 so line numbers are different. > > I will open a jira. > > On Wed, Dec 7, 2011 at 7:34 PM, Stack <[email protected]> wrote: > >> On Wed, Dec 7, 2011 at 5:30 PM, Shrijeet Paliwal >> <[email protected]> wrote: >> > Hi, >> > Version in which I observed issue: 0.90.3 + RPC timeout patch >> > Version affected : trunk >> > >> > Stack trace: >> > >> > 2011-11-30 13:10:26,557 [IPC Client (47) connection to >> > inw-68.rfiserve.net/172.22.4.68:60020 from an unknown user] WARN >> > org.apache.hadoop.ipc.HBaseClient - Unexpected exception receiving call >> > responses >> > java.lang.NullPointerException >> >>-at >> > >> org.apache.hadoop.hbase.ipc.HBaseClient$Connection.receiveResponse(HBaseClient.java:583) >> >>-at >> > >> org.apache.hadoop.hbase.ipc.HBaseClient$Connection.run(HBaseClient.java:511) >> > >> > I think line number #3 here http://pastie.org/2983633 may return a null >> > 'call'. It is so because if you rpc timeout enable, we proactively >> clean up >> > other calls which have expired their lifetime along with the call for >> which >> > socket >> > timeout exception happend (refer to this method : private void >> > cleanupCalls(long rpcTimeout)) . >> > >> > Please let me know if what I am thinking makes sense. >> > >> >> Is line #583 in your HBaseClient line #14 in your pastebin? (When I >> look at 0.90.3 tag, line #583 takes me someplace unrelated: >> >> http://svn.apache.org/viewvc/hbase/tags/0.90.3/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java?revision=1125027&view=markup >> ) >> >> Your reasoning seems fine to me. >> >> St.Ack >> > >
