| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2072985 | 5.0 | Devananda Jayaraman | P4 | Resolved | Fixed | tiger |
| JDK-2072984 | 1.4.2_02 | Devananda Jayaraman | P4 | Resolved | Fixed | 02 |
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.
###@###.###
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.
###@###.###
- backported by
-
JDK-2072984 extra pings to server if WeakReferenced CachedJarLoaders gc'ed
-
- Resolved
-
-
-
- Resolved
-