[
https://issues.apache.org/jira/browse/HDFS-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255268#comment-15255268
]
Hudson commented on HDFS-9905:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9661 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9661/])
HDFS-9905. WebHdfsFileSystem#runWithRetry should display original stack
(iwasakims: rev 6fcde2e38da04cae3aad6b13cf442af211f71506)
*
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/web/TestWebHdfsTimeouts.java
*
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/web/WebHdfsFileSystem.java
> WebHdfsFileSystem#runWithRetry should display original stack trace on error
> ---------------------------------------------------------------------------
>
> Key: HDFS-9905
> URL: https://issues.apache.org/jira/browse/HDFS-9905
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.7.3
> Reporter: Kihwal Lee
> Assignee: Wei-Chiu Chuang
> Attachments: HDFS-9905.001.patch, HDFS-9905.002.patch
>
>
> When checking for a timeout in {{TestWebHdfsTimeouts}}, it does get
> {{SocketTimeoutException}}, but the message sometimes does not contain
> "connect timed out". Since the original exception is not logged, we do not
> know details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
