[
https://issues.apache.org/jira/browse/HADOOP-8419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579875#comment-13579875
]
Eric Yang commented on HADOOP-8419:
-----------------------------------
Matt, the failures is not related to this patch in HDFS trunk failure case.
HDFS test case is failing due to HADOOP-9067. I also reverted this patch
completely and reran the test case to be sure that this patch was not trigger
any strange hidden behavior.
Amir, the test case has been tested on power platform on ppc Jenkins server.
We did not see the regression issue that you mentioned. Could you provide IBM
JDK version number that has this regression fixed in zLinux? This will help us
to make sure the logic is only target specific version ranges of IBM jdk that
have this bug. Since you are using the same ppc Jenkins server to do the test,
I don't think you will see any regression. I am inclined to close this issue
baring no objections.
> 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
> Fix For: 1.1.2
>
> 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
