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

Yu Li commented on HADOOP-8419:
-------------------------------

Test result on trunk:

Both with and w/o my patch, below UT case failed, but from error message it 
should be irrelavant with compression:
=======================================================
Tests in error:
  testRDNS(org.apache.hadoop.net.TestDNS): DNS server failure [response code 2]

Tests run: 1784, Failures: 0, Errors: 1, Skipped: 18

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Hadoop Main ................................ SUCCESS [1.702s]
[INFO] Apache Hadoop Project POM ......................... SUCCESS [3.812s]
[INFO] Apache Hadoop Annotations ......................... SUCCESS [1.312s]
[INFO] Apache Hadoop Project Dist POM .................... SUCCESS [0.245s]
[INFO] Apache Hadoop Assemblies .......................... SUCCESS [0.335s]
[INFO] Apache Hadoop Auth ................................ SUCCESS [6.754s]
[INFO] Apache Hadoop Auth Examples ....................... SUCCESS [0.322s]
[INFO] Apache Hadoop Common .............................. FAILURE [16:42.921s]
[INFO] Apache Hadoop Common Project ...................... SKIPPED
=======================================================

>From the UT log we could see below error message:
=======================================================
Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 15.459 sec <<< 
FAILURE!
testRDNS(org.apache.hadoop.net.TestDNS)  Time elapsed: 15233 sec  <<< ERROR!
javax.naming.ServiceUnavailableException: DNS server failure [response code 2]; 
remaining name '81.122.30.9.in-addr.arpa'
        at com.sun.jndi.dns.DnsClient.checkResponseCode(DnsClient.java:594)
        at com.sun.jndi.dns.DnsClient.isMatchResponse(DnsClient.java:553)
=======================================================
                
> GzipCodec NPE upon reset with IBM JDK
> -------------------------------------
>
>                 Key: HADOOP-8419
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8419
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: io
>    Affects Versions: 1.0.3
>            Reporter: Luke Lu
>            Assignee: Yu Li
>              Labels: gzip, ibm-jdk
>         Attachments: HADOOP-8419-branch-1.patch, HADOOP-8419-trunk.patch
>
>
> The GzipCodec will NPE upon reset after finish when the native zlib codec is 
> not loaded. When the native zlib is loaded the codec creates a 
> CompressorOutputStream that doesn't have the problem, otherwise, the 
> GZipCodec uses GZIPOutputStream which is extended to provide the resetState 
> method. Since IBM JDK 6 SR9 FP2 including the current JDK 6 SR10, 
> GZIPOutputStream#finish will release the underlying deflater, which causes 
> NPE upon reset. This seems to be an IBM JDK quirk as Sun JDK and OpenJDK 
> doesn't have this issue.

--
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