United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6661811 Web Start 1.6.0_3 causes repeated download of jar files
6661811 : Web Start 1.6.0_3 causes repeated download of jar files

Details
Type:
Bug
Submit Date:
2008-02-11
Status:
Closed
Updated Date:
2010-11-04
Project Name:
JDK
Resolved Date:
2008-07-03
Component:
deploy
OS:
windows_xp
Sub-Component:
webstart
CPU:
x86
Priority:
P3
Resolution:
Fixed
Affected Versions:
6u2
Fixed Versions:
6u10

Related Reports
Relates:

Sub Tasks

Description
FULL PRODUCT VERSION :
JRE 1.6.0 Update 3

ADDITIONAL OS VERSION INFORMATION :
Any versions of Windows XP

A DESCRIPTION OF THE PROBLEM :

For some customers on Web start 1.6.0_3, they are getting repeated downloads of their jar files.  It appears to be an issue with the the way version 1.6 does caching.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :

Invoke this app to bring up the login panel and then exit from login panel.
http://baliweb.etrade.com/balicli_alt1/etrader.jnlp

Relaunch app a second time.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -

The second launch should NOT result in another download.
ACTUAL -

For some customers, they are seeing a download everytime of the jar files.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :

The only workaround right now is to revert back to previous versions of Web start.

Release Regression From : 6u2
The above release value was the last known release where this 
bug was not reproducible. Since then there has been a regression.

                                    

Comments
EVALUATION

Allow multiple cache entry of the same URL to exists in the cache, if they have the same URL but different codebase host IP.  Whenever we load a cached JAR, we make sure the cached IP address(if available) matches the IP address lookup of the codebase host currently.  This limits the maximum number of JAR download to the number of IP address a codebase host can have.

Cache entry update will be applied to the entry of the matching codebase IP address only.

Also changes the cache viewer to adapt to this change.   We will not display duplicate cache entry because of the different IP address.  when the user choose to remove a cache entry from the cache viewer, we remove all instances (different codebase IP address) of the cache entry.
                                     
2008-03-18



Hardware and Software, Engineered to Work Together