You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/09/26 19:46:34 UTC
[jira] [Updated] (HADOOP-11143) NetUtils.wrapException loses inner
stack trace on BindException
[ https://issues.apache.org/jira/browse/HADOOP-11143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-11143:
------------------------------------
Attachment: HADOOP-11143-001.patch
patch which has the bind exception mimic the rest of the methods; includes the nested strace
> 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
> 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)