|
Quick Lists
|
|
Bug ID:
|
4901951
|
|
Votes
|
0
|
|
Synopsis
|
extra pings to server if WeakReferenced CachedJarLoaders gc'ed
|
|
Category
|
java_plugin:misc
|
|
Reported Against
|
1.4.2
|
|
Release Fixed
|
1.4.1_07
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
06-AUG-2003
|
|
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.
xxxxx@xxxxx
|
|
Work Around
|
increase the heap size using -Xmx
xxxxx@xxxxx
|
|
Evaluation
|
Description explains the cause
xxxxx@xxxxx 2003-08-06
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
