[
https://issues.apache.org/jira/browse/HADOOP-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731100#comment-13731100
]
Steve Loughran commented on HADOOP-9844:
----------------------------------------
Patching my local build to fix this shows that the root cause is that
{{IpcException}} caches its error string locally, so {{getMessage()}} returns
null. The base class toString() falls back to the exception type
{code}
2013-08-06 11:40:18,642 [Socket Reader #1 for port 60624] INFO ipc.Server
(Server.java:doRead(800)) - IPC Server listener on 60624: readAndProcess from
client 127.0.0.1 threw exception [org.apache.hadoop.ipc.IpcException]
org.apache.hadoop.ipc.IpcException
at
org.apache.hadoop.ipc.Server$Connection.initializeAuthContext(Server.java:1547)
at
org.apache.hadoop.ipc.Server$Connection.readAndProcess(Server.java:1507)
at org.apache.hadoop.ipc.Server$Listener.doRead(Server.java:791)
at
org.apache.hadoop.ipc.Server$Listener$Reader.doRunLoop(Server.java:590)
at org.apache.hadoop.ipc.Server$Listener$Reader.run(Server.java:565)
{code}
> NPE when trying to create an error message response of RPC
> ----------------------------------------------------------
>
> Key: HADOOP-9844
> URL: https://issues.apache.org/jira/browse/HADOOP-9844
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.1.1-beta
> Reporter: Steve Loughran
>
> I'm seeing an NPE which is raised when the server is trying to create an
> error response to send back to the caller and there is no error text.
> The root cause is probably somewhere in SASL, but sending something back to
> the caller would seem preferable to NPE-ing server-side.
--
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
