[
https://issues.apache.org/jira/browse/HADOOP-11143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151084#comment-14151084
]
Hudson commented on HADOOP-11143:
---------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #694 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/694/])
HADOOP-11143 NetUtils.wrapException loses inner stack trace on BindException
(stevel: rev 7f300bcdc78d164a42d56c3f65a512cfe0ac40be)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NetUtils.java
* hadoop-common-project/hadoop-common/CHANGES.txt
> NetUtils.wrapException loses inner stack trace on BindException
> ---------------------------------------------------------------
>
> Key: HADOOP-11143
> URL: https://issues.apache.org/jira/browse/HADOOP-11143
> Project: Hadoop Common
> Issue Type: Bug
> Components: net
> Affects Versions: 2.5.1
> Environment: machine that doesn't bind
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 2.6.0
>
> Attachments: HADOOP-11143-001.patch
>
>
> {{NetUtils.wrapException}} is designed to aid debugging by including
> exception diagnostics in the wrapped & relayed exception.
> When a BindException is caught, we build the new exception but don't include
> the original as the inner cause.
> this means it doesn't get logged, and while the host:port problem may be
> identifiable, the bit of the code playing up is now harder to track down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
