You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2014/04/02 03:04:41 UTC

[jira] [Resolved] (HADOOP-10455) When there is an exception, ipc.Server should first check whether it is an terse exception

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

Tsz Wo Nicholas Sze resolved HADOOP-10455.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.1
     Hadoop Flags: Reviewed

I have committed this.

> When there is an exception, ipc.Server should first check whether it is an terse exception
> ------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-10455
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10455
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>             Fix For: 2.4.1
>
>         Attachments: c10455_20140401.patch, c10455_20140401b.patch
>
>
> ipc.Server allows application servers to define terse exceptions; see Server.addTerseExceptions.  For terse exception, it only prints a short message but not the stack trace.  However, if an exception is both RuntimeException and terse exception, it still prints out the stack trace of the exception.



--
This message was sent by Atlassian JIRA
(v6.2#6252)