JDK-6740193 : bug in Java Webstart Caching when using large argument list on resource href.
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 5.0u16
  • Priority: P1
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-08-22
  • Updated: 2010-12-07
  • Resolved: 2009-07-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
6u11-revFixed 7 b64Fixed
The problem can be reproduced each time, if you have both 1.6.0 and 1.5.0 installed.
If only 1.5.0 installed (1.5.0_11 through 1.5.0_16), there is No problem.
If only 1.6.0 installed there is No problem. 

1) save the two attachments on a PC
2) modify singleapp.jnlp to point to helloSinged.jar
                  codebase='file:///C:\Documents and Settings\user\Desktop'>
3) double click on the JNLP file
4) notice the exception

java.lang.ClassNotFoundException: HelloWorld
	at java.net.URLClassLoader$1.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(Unknown Source)
	at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
	at com.sun.javaws.Launcher.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

Customer is experiencing this on Webserver accessing the JNLP file via a Servlet.
We took out the Servlet out of the picture to make it easy to reproduce and avoid deploying it on a Web/App server here.

From ###@###.###:
This is a bug in our caching and I will look into where it comes from.

EVALUATION The fix for this (uncverified) was delivered into JDK7 b64 as part of: 6797688: Umbrella: Merge all JDK 6u4 - 6u12 deployment code into JDK7

EVALUATION see comments