[
https://issues.apache.org/jira/browse/HADOOP-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551096#comment-13551096
]
Hudson commented on HADOOP-8419:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #1282 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1282/])
HADOOP-8419. Fixed GzipCode NPE reset for IBM JDK. (Yu Li via eyang)
(Revision 1431740)
HADOOP-8419. Fixed GzipCode NPE reset for IBM JDK. (Yu Li via eyang) (Revision
1431739)
Result = FAILURE
eyang : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1431740
Files :
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/io/compress/TestCompressionStreamReuse.java
eyang : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1431739
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/GzipCodec.java
> 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-branch1-v2.patch, HADOOP-8419-trunk.patch,
> HADOOP-8419-trunk-v2.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
