JDK-6189465 : More error detail when encountering problems reading Zip files.
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.jar
  • Affected Version: 1.4.2_05,6u7
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: linux,solaris_8
  • CPU: generic,x86
  • Submitted: 2004-11-02
  • Updated: 2010-08-18
Related Reports
Duplicate :  
JDK-6738211 - ZipFile.open error message fails to include path to (potentially corrupt) ZIP file
Relates :  
JDK-6190121 - Jar is not usable for testing integrity of Jar files.
Relates :  
JDK-6189491 - Silent failure of corrupt Jar/Zip files during classloading yields poor diagnosability.
Description
Java's native routines for reading Zip files can return detailed error
messages, but often don't.  The exception therefore usually just says:

	"error in opening zip file"

The mechanism for reporting in more detail is already there, and a more 
specific error message would help diagnose problems: even if the main 
point they communicate is "the zip file was found, there is no permissions
problem, but some problem internal to the zip file".
###@###.### 11/2/04 15:16 GMT
Comments
EVALUATION A debug, non-production-only system property would be a reasonable way of allowing filenames to be printed in exceptions.
26-08-2008
EVALUATION Adding the path name to exception messages is likely to cause security issues (typically cache/temporary-file location disclosure).
19-08-2008
EVALUATION At the very least, the pathname of the offending file should be printed.
18-08-2008
EVALUATION The file zip_util.c is being reworked by the TL group, I am assigning this to the TL group for further evaluation. ###@###.### 2005-1-25 23:52:58 GMT
02-11-2004