Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <6191144.15851274726670840.JavaMail.jira@thor>
Date: Mon, 24 May 2010 14:44:30 -0400 (EDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6723) unchecked exceptions thrown in IPC
 Connection orphan clients
In-Reply-To: <33033218.184741272223549956.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HADOOP-6723:
--------------------------------

Integrated in Hadoop-Common-trunk-Commit #264 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/264/])
    HADOOP-6723.  Unchecked exceptions thrown in IPC Connection should not orphan clients.  Contributed by Todd Lipcon.


> unchecked exceptions thrown in IPC Connection orphan clients
> ------------------------------------------------------------
>
>                 Key: HADOOP-6723
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6723
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.20.2
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.21.0
>
>         Attachments: hadoop-6723.txt
>
>
> If the server sends back some malformed data, for example,  receiveResponse() can end up with an incorrect call ID. Then, when it tries to find it in the calls map, it will end up with null and throw NPE in receiveResponse. This isn't caught anywhere, so the original IPC client ends up hanging forever instead of catching an exception. Another example is if the writable implementation itself throws an unchecked exception or OOME.
> We should catch Throwable in Connection.run() and shut down the connection if we catch one.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.