[
https://issues.apache.org/jira/browse/HADOOP-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957642#comment-13957642
]
Hudson commented on HADOOP-10455:
---------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1745 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1745/])
HADOOP-10455. When there is an exception, ipc.Server should first check whether
it is an terse exception. (szetszwo:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1583842)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
> 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)
