[
https://issues.apache.org/jira/browse/YARN-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731064#comment-13731064
]
Steve Loughran commented on YARN-1035:
--------------------------------------
Looking up the stack, it's in
{code}
private void doSaslReply(Exception ioe) throws IOException {
setupResponse(authFailedResponse, authFailedCall,
RpcStatusProto.FATAL, RpcErrorCodeProto.FATAL_UNAUTHORIZED,
null, ioe.getClass().getName(), ioe.getLocalizedMessage());
responder.doRespond(authFailedCall);
}
{code}
This code assumes that the {{ioe.getLocalizedMessage()}} always returns a
non-null string. Some exceptions do return null. For a robust response,
{{ioe.toString()}} should be used.
> NPE when trying to create an error message response of RPC
> ----------------------------------------------------------
>
> Key: YARN-1035
> URL: https://issues.apache.org/jira/browse/YARN-1035
> Project: Hadoop YARN
> 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
