JDK-4901951 : extra pings to server if WeakReferenced CachedJarLoaders gc'ed
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-08-06
  • Updated: 2003-11-12
  • Resolved: 2003-08-18
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 Other
1.4.1_07 07Fixed 1.4.2_02Fixed
Description
Jar files cached using cache_archive or cache_archive_ex can sometimes ping the
server checking for expirary date. This is because JarCache.loadedJars uses 
WeakReferences for CachedJarLoader's and these can be gc'ed at any time.

If the jar is loaded once from the cache it is removed from JarCache.currentJars
in JarCache.get() and added to the JarCache.loadedJars. Because loadedJars uses 
WeakReferences then it maybe removed by gc and when the jar is requested to be 
loaded again it is no longer in curentJars, and then the extra ping. 

###@###.###
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.1_07 1.4.2_02 generic tiger FIXED IN: 1.4.1_07 1.4.2_02 tiger INTEGRATED IN: 1.4.1_07 1.4.2_02 tiger
14-06-2004
WORK AROUND increase the heap size using -Xmx ###@###.###
11-06-2004
EVALUATION Description explains the cause ###@###.### 2003-08-06
06-08-2003