-
Bug
-
Resolution: Fixed
-
P2
-
6
-
b90
-
x86
-
windows_xp
FULL PRODUCT VERSION :
java version "1.6.0-beta2"
Java(TM) SE Runtime Environment (build 1.6.0-beta2-b84)
Java HotSpot(TM) Client VM (build 1.6.0-beta2-b84, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
XP Pro SP2
A DESCRIPTION OF THE PROBLEM :
In the Web Start application below, if accessed with Java 1.4 or 5.0 local cache of jars is used (to be expected)
If Java 6 is used Web Start attempts to load every class from the server (even though the jars are in the client's cache). As a result loading is extremelly slow, although the application does eventually (minutes down the road) start.
It does not appear to be a JNLP file problem as the same JNLP pointing to to updated jars does not behave the same way.
Web Page:
http://www.insitechinc.com/demo.php3
Direct JNLP Link
http://www.insitechinc.com/STOCKTRADER/demo/stocktrader.jnlp
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Access the following JNLP Link using JDK 6 to get the problem
http://www.insitechinc.com/STOCKTRADER/demo/stocktrader.jnlp
Access the same link using JDK 1.4 or 5.0 and everything works.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
cached jars should be used to load classes from.
ACTUAL -
jars are downloaded from the server
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 5.0u7
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.
java version "1.6.0-beta2"
Java(TM) SE Runtime Environment (build 1.6.0-beta2-b84)
Java HotSpot(TM) Client VM (build 1.6.0-beta2-b84, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
XP Pro SP2
A DESCRIPTION OF THE PROBLEM :
In the Web Start application below, if accessed with Java 1.4 or 5.0 local cache of jars is used (to be expected)
If Java 6 is used Web Start attempts to load every class from the server (even though the jars are in the client's cache). As a result loading is extremelly slow, although the application does eventually (minutes down the road) start.
It does not appear to be a JNLP file problem as the same JNLP pointing to to updated jars does not behave the same way.
Web Page:
http://www.insitechinc.com/demo.php3
Direct JNLP Link
http://www.insitechinc.com/STOCKTRADER/demo/stocktrader.jnlp
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Access the following JNLP Link using JDK 6 to get the problem
http://www.insitechinc.com/STOCKTRADER/demo/stocktrader.jnlp
Access the same link using JDK 1.4 or 5.0 and everything works.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
cached jars should be used to load classes from.
ACTUAL -
jars are downloaded from the server
REPRODUCIBILITY :
This bug can be reproduced always.
Release Regression From : 5.0u7
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.