[HDFS-11059] TestWebHdfsTimeouts fails due to null SocketTimeoutException

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 3.0.0-alpha2
• Component/s: webhdfs
• Target Version/s: 3.0.0-alpha4
• Assignee: John Zhuge
• Reporter: John Zhuge
• Created: 26/Oct/16 01:57
• Updated: 29/Jan/17 07:13
• Resolved: 29/Jan/17 07:13

Description

TestWebHdfsTimeouts expects SocketTimeoutException with "connect timed out" or "Read timed out" message but fails when encountering "null" message sometimes. Occurred 4 out of 100 tests.

SocksSocketImpl#remainingMillis may send null SocketTimeoutException:

    private static int remainingMillis(long deadlineMillis) throws IOException {
        if (deadlineMillis == 0L)
            return 0;

        final long remaining = deadlineMillis - System.currentTimeMillis();
        if (remaining > 0)
            return (int) remaining;

        throw new SocketTimeoutException();   <<<<==
    }

Issue Links

• relates to: HDFS-11043 TestWebHdfsTimeouts fails