hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12178) NPE during handling of SASL setup if problem with SASL resolver class
Date Mon, 13 Jul 2015 10:59:05 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steve Loughran updated HADOOP-12178:
------------------------------------
    Attachment: HADOOP-12178-001.patch

Here is a patch which only treats IOEs as potentially handle-able, and even there has checks
to avoid an NPE.

I could not think of an easy way to test this: suggestions welcome. Otherwise, careful review
is encouraged

> NPE during handling of SASL setup if problem with SASL resolver class
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-12178
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12178
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 2.7.1
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-12178-001.patch
>
>
> If there's any problem in the constructor of {{SaslRpcClient}}, then IPC Client throws
an NPE rather than forwarding the stack trace. This is because the exception handler assumes
that {{saslRpcClient}} is not null, that the exception is related to the SASL setup itself.
> The exception handler needs to check for {{saslRpcClient}} being null, and if so, rethrow
the exception



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message