[jira] [Commented] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on HADOOP-8661:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12550509/HADOOP-8661.txt
  against trunk revision 1556f86.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5131//console

This message is automatically generated.

> RemoteException's Stack Trace would be better returned by getStackTrace
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-8661
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8661
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>    Affects Versions: 0.23.3, 2.0.0-alpha, 3.0.0
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>         Attachments: HADOOP-8661.txt, HADOOP-8661.txt, HADOOP-8661.txt
>
>
> It looks like all exceptions produced by RemoteException include the full stack trace of the original exception in the message.  This is different from 1.0 behavior to aid in debugging, but it would be nice to actually parse the stack trace and return it through getStackTrace instead of through getMessage.



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