JDK-8264048 : Fix caching in Jar URL connections when an entry is missing
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-03-23
  • Updated: 2021-04-12
  • Resolved: 2021-04-06
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.
JDK 17
17 b17Fixed
Related Reports
Duplicate :  
JDK-8132359 - Amend JarURLConnection::getJarFile() to return JarFile object reference for nonexistent JAR file entry URL
Relates :  
JDK-8132359 - Amend JarURLConnection::getJarFile() to return JarFile object reference for nonexistent JAR file entry URL
Description
When an URL connection is referencing an entry that doesn't exist in a Jar file the Jar file is cached before an exception is thrown, but the Jar file can't be obtained from the failed connection, which prevents the caller, for instance a URLClassLoader, from closing it.
Comments
Changeset: a611c462 Author: Aleksei Efimov <aefimov@openjdk.org> Date: 2021-04-06 10:43:59 +0000 URL: https://git.openjdk.java.net/jdk/commit/a611c462
06-04-2021