Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1577353752.1257190259436.JavaMail.jira@brutus>
Date: Mon, 2 Nov 2009 19:30:59 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6343) Stack trace of any runtime
 exceptions should be recorded in the server logs.
In-Reply-To: <633519870.1256848799736.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tsz Wo (Nicholas), SZE commented on HADOOP-6343:
------------------------------------------------

I suggest committing this to 0.20.  Otherwise, it is hard to fix bugs like HDFS-626.

> Stack trace of any runtime exceptions should be recorded in the server logs. 
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-6343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6343
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6343.1.patch, HADOOP-6343.2.patch
>
>
> Hadoop RPC catches any server side exception and throws an IOException. Runtime excpetions should be recorded in the server logs before being thrown as IOException.

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