Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 17 May 2011 18:03:47 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <588371746.19922.1305655427516.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <903601160.6842.1305210828211.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7282) getRemoteIp could return null in
 cases where the call is ongoing but the ip went away.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034923#comment-13034923 ] 

Hudson commented on HADOOP-7282:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #606 (See [https://builds.apache.org/hudson/job/Hadoop-Common-trunk-Commit/606/])
    HADOOP-7282. ipc.Server.getRemoteIp() may return null.  Contributed by John George


> getRemoteIp could return null in cases where the call is ongoing but the ip went away.
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7282
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7282
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>            Reporter: John George
>            Assignee: John George
>             Fix For: 0.23.0
>
>         Attachments: HADOOP-7282-1.patch, HADOOP-7282.patch, diffs.txt
>
>
> getRemoteIp gets the ip from socket instead of the stored ip in Connection object. Thus calls to this function could return null when a client disconnected, but the rpc call is still ongoing...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira