[
https://issues.apache.org/jira/browse/HADOOP-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329059#comment-14329059
]
Jason Lowe commented on HADOOP-9844:
------------------------------------
I recently ran into another case that's similar to this. Stack trace on the
server:
{noformat}
java.lang.NullPointerException
at
org.apache.hadoop.ipc.protobuf.RpcHeaderProtos$RpcResponseHeaderProto$Builder.setErrorMsg(RpcHeaderProtos.java:2903)
at org.apache.hadoop.ipc.Server.setupResponse(Server.java:2339)
at org.apache.hadoop.ipc.Server.access$2700(Server.java:130)
at
org.apache.hadoop.ipc.Server$Connection.processOneRpc(Server.java:1802)
at
org.apache.hadoop.ipc.Server$Connection.readAndProcess(Server.java:1555)
at org.apache.hadoop.ipc.Server$Listener.doRead(Server.java:787)
at
org.apache.hadoop.ipc.Server$Listener$Reader.doRunLoop(Server.java:661)
at org.apache.hadoop.ipc.Server$Listener$Reader.run(Server.java:632)
{noformat}
Yet another case where getMessage() on an exception must be null.
Unfortunately I don't think the proposed patch will address this particular
case. I think we need the original proposed fix and also some null message
protection in setupReponse in case we just don't have an error message for some
reason.
> 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: 3.0.0, 2.1.1-beta, 2.6.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-9844-001.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
