解压 war/jar文件时出现以下错误:
java.util.zip.ZipException: invalid distance too far back
at org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readFromInflater(ZipArchiveInputStream.java:478)
at org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readDeflated(ZipArchiveInputStream.java:443)
at org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.read(ZipArchiveInputStream.java:384)
at java.io.InputStream.read(Unknown Source)
at org.apache.commons.compress.utils.IOUtils.copy(IOUtils.java:75)
at org.apache.commons.compress.utils.IOUtils.copy(IOUtils.java:56)
at com.xunge.AESFileEncoder$1.run(AESFileEncoder.java:149)
at java.lang.Thread.run(Unknown Source)
Caused by: java.util.zip.DataFormatException: invalid distance too far back
at java.util.zip.Inflater.inflateBytes(Native Method)
at java.util.zip.Inflater.inflate(Unknown Source)
at org.apache.commons.compress.archivers.zip.ZipArchiveInputStream.readFromInflater(ZipArchiveInputStream.java:476)
… 7 more
相关代码:
PipedInputStream pin = new PipedInputStream();
PipedOutputStream pout = new PipedOutputStream(pin);
new Thread(new Runnable() {
public void run() {
try {
IOUtils.copy(ais, pout);
pout.close();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}).start();
ArchiveInputStream inJar = new ArchiveStreamFactory()
.createArchiveInputStream(ArchiveStreamFactory.JAR,
pin);
以上代码是没有问题,如果使用 pin 的代码和 pin 的声明代码中间隔了太多的代码就会产生此异常。具体没有做试验,也可能是有逻辑判断语句的原因。

本文探讨了解压WAR或JAR文件时遇到的java.util.zip.ZipException错误:invalid distance too far back。通过分析代码示例,指出问题可能源于PipedInputStream的使用方式,特别是当其声明与使用之间间隔过多代码或存在逻辑判断时。文章提供了详细的异常堆栈跟踪信息。
2696

被折叠的 条评论
为什么被折叠?



