United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-4901951 extra pings to server if WeakReferenced CachedJarLoaders gc'ed
JDK-4901951 : extra pings to server if WeakReferenced CachedJarLoaders gc'ed

Details
Type:
Bug
Submit Date:
2003-08-06
Status:
Resolved
Updated Date:
2003-11-12
Project Name:
JDK
Resolved Date:
2003-08-18
Component:
deploy
OS:
generic
Sub-Component:
plugin
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
1.4.2
Fixed Versions:
1.4.1_07 (07)

Related Reports
Backport:
Backport:

Sub Tasks

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
EVALUATION

Description explains the cause
###@###.### 2003-08-06
                                     
2003-08-06
WORK AROUND

increase the heap size using -Xmx

###@###.###
                                     
2004-06-11
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


                                     
2004-06-14



Hardware and Software, Engineered to Work Together