hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8661) RemoteException's Stack Trace would be better returned by getStackTrace
Date Tue, 23 Oct 2012 18:29:13 GMT

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

Robert Joseph Evans updated HADOOP-8661:

    Attachment: HADOOP-8661.txt

just an up-merge. It would be nice if someone could review this so I don't have to keep it
up to date.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message