JDK-4265719 : jarsigner: unable to sign jar: ZipException: invalid entry compressed size
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util
  • Affected Version: 1.3.0
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_2.5.1
  • CPU: sparc
  • Submitted: 1999-08-25
  • Updated: 2020-10-03
  • Resolved: 1999-09-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.3.0 kestrelFixed
Related Reports
Relates :  
Description
Happens in 1.2.2 and 1.3 beta on Windows NT 4.0

I was trying to sign jmf.jar.
It signs a whole bunch of files.

Then you get
signing: hm20action.class
jarsigner:  unable to sign jar: ZipException: invalid entry compressed size
(expected 7789 but got 7758 bytes)

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: kestrel FIXED IN: kestrel INTEGRATED IN: kestrel
14-06-2004

EVALUATION jan.luehe@Eng 1999-08-25 This looks like a ZIP problem. We used to have a similar one before on Solaris. When JarSigner copies zip entries from the input zip file to the output zip file, new zip entries need to be created, instead of writing out the zip entries which are read from the input. Different versions of the compression algorithm might generate different compressed size. ###@###.### 1999-09-07
07-09-1999