[
https://issues.apache.org/jira/browse/HDFS-9905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242127#comment-15242127
]
Masatake Iwasaki commented on HDFS-9905:
----------------------------------------
bq. I don't know what would cause SocketTimeoutException to give a null message
instead of the expected Read timed out.
Though underlying implementation of
[PlainSocketImpl|http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/file/34c594b52b73/src/solaris/native/java/net/PlainSocketImpl.c]
and
[SocketInputStream|http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/file/34c594b52b73/src/solaris/native/java/net/SocketInputStream.c]
throws SocketTimeoutException with expected message, SocketTimeoutException
without message could be thrown by {{SocksSocketImpl#remainingMillis}} before
reaching to those code paths if connect timeout is set to very small value.
I'm +1 on the fix of {{WebHdfsFileSystem#AbstractRunner#runWithRetry}}
suggested by [~eepayne] in addition to 001.
> TestWebHdfsTimeouts fails occasionally
> --------------------------------------
>
> 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
>
>
> When checking for a timeout, 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)
