[ 
https://issues.apache.org/jira/browse/HDFS-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600627#comment-13600627
 ] 

Hudson commented on HDFS-4013:
------------------------------

Integrated in Hadoop-trunk-Commit #3456 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/3456/])
    HDFS-4013. TestHftpURLTimeouts throws NPE. Contributed by Chao Shi. 
(Revision 1455755)

     Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1455755
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestHftpURLTimeouts.java

                
> TestHftpURLTimeouts throws NPE
> ------------------------------
>
>                 Key: HDFS-4013
>                 URL: https://issues.apache.org/jira/browse/HDFS-4013
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>         Environment: java version "1.7.0_06-icedtea"
> OpenJDK Runtime Environment (fedora-2.3.1.fc17.2-i386)
> OpenJDK Client VM (build 23.2-b09, mixed mode)
>            Reporter: Chao Shi
>            Assignee: Chao Shi
>            Priority: Trivial
>             Fix For: 2.0.5-beta
>
>         Attachments: hdfs-4013.patch, hdfs-4013.patch, hdfs-4013.patch
>
>
> The case fails at line 116, where message is null. I guess this may be an 
> openjdk-specific behavior, but it would be nice to have it fixed although 
> openjdk is not officially supported.
> FYI: The exception is thrown with null message at java.net.SocksSocketImpl.
> {code}
>     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();
>     }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to