JDK-6826801 : JarFileFactory should not use HashMap
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 6
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-04-06
  • Updated: 2010-04-04
  • Resolved: 2009-08-14
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 6 JDK 7
6u18Fixed 7 b70Fixed
Related Reports
Relates :  
JDK-6797730 - Umbrella: Applet startup performance improvements
Relates :  
JDK-6826780 - URLClassPath should use HashMap instead of HashMap
Relates :  
JDK-6826789 - SecureClassLoader should not use CodeSource URLs as HashMap keys
Relates :  
JDK-6810437 - URL.hashcode() and URL.equals() are greedy with DN lookups
Description
both windows and solaris implementations of cache in the JarFileFactory use HashMap<URL> and this may cause 
DNS useless lookups.
Comments
EVALUATION Replace the URL key with a String representation of the url. see the evaluation section of 6826780. changeset: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/9424d836691f
07-08-2009