-
Bug
-
Resolution: Unresolved
-
P4
-
None
-
6
-
generic
-
generic
When the classloader encounters a malformed JAR it keeps going as
if nothing has happened, and later produces a irrelevant ClassNotFoundException. The lack of error reporting can cost a lot
of time trying to debug applications, especially complicated ones, which
download JARs from the network.
###@###.### 2005-03-10 20:06:15 GMT
if nothing has happened, and later produces a irrelevant ClassNotFoundException. The lack of error reporting can cost a lot
of time trying to debug applications, especially complicated ones, which
download JARs from the network.
###@###.### 2005-03-10 20:06:15 GMT
- relates to
-
JDK-6236704 bad jar files ignored in extension and endorsed dirs
- Resolved
-
JDK-6237956 mustang b25 cannot extract data from zip files created by third-party zip implementations
- Closed
-
JDK-6189491 Silent failure of corrupt Jar/Zip files during classloading yields poor diagnosability.
- Closed