FULL PRODUCT VERSION :
jre 1.6.0_10, 1.6.0_11_b03
ADDITIONAL OS VERSION INFORMATION :
Windows XP SP3, Windows Vista
EXTRA RELEVANT SYSTEM CONFIGURATION :
No special configuration required.
A DESCRIPTION OF THE PROBLEM :
The bug number 6507009 occurs again since JRE 1.6.0_10. Running a downloaded Webstart application offline does not work using the runtimes mentioned above.
The problem does not occur with JRE 1.6.0_07.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1.) Add the the demo application 'Notepad.jar' contained in the JDK 1.6.0_07 to an arbitrary web server.
2.) Add a JNLP-file 'Notepad.jnlp' with the following content to the same directory (correct the 'codebase' to fit your webserver needs):
<jnlp spec="1.5+" codebase="http://myserver.com/javaws/" href="Notepad.jnlp">
<title>Notepad Demo Application</title>
<description>Shows that Webstart 1.6.0_11 does not work for offline start</description>
<j2se version="1.5.0_14+" />
3.) Install JRE or JDK 1.6.0_11 on a Windows XP or Vista computer.
4.) On the command line run
This downloads and runs the notepad demo application.
5.) On the command line run javaws -viewer
This shows, that the application was downloaded and is present in the application cache.
5.) Pull out the notwork cable or deaktivate the LAN connection. If you like, restart the computer.
6.) On the command line run again
The application should run offline now, but an error is shown, that the JNLP-file cannot be downloaded.
7.) Uninstall every JDK above 1.6.0_07 (1.6.0_10 and/or 1.6.0_11)
8.) Install JDK 1.6.0_07.
9.) Repeat steps 4, 5, 6.
In step 6, the application starts offline without any problem.
EXPECTED VERSUS ACTUAL BEHAVIOR :
Offline application does not start. Same error as in bug 6507009.
Same error as in bug 6507009.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
See bug 6507009.
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
No workaround possible using the above runtimes. Everything works well using JRE 1.6.0_07.
Release Regression From : 6u7
The above release value was the last known release where this
bug was not reproducible. Since then there has been a regression.