FULL PRODUCT VERSION :
java version "1.6.0_19"
Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
Java HotSpot(TM) Client VM (build 16.2-b04, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.0.6001]

A DESCRIPTION OF THE PROBLEM :
Unable to launch my Java Web Start application.
When I clear the Java Web Start temporary files, the application launches fine.
However I am unable to launch the application again.
When I try to launch the application again, I receive a Java Web Start error dialog box. The full error text has been provided in the "Error Messages" portion of this bug report.

Every time that I clear the Java Web Start temp files, I am able to launch the application, but only once. Subsequent attempts to launch the application result in the same error. Thus, it seems that this error is related to the caching mechanism of Java Web Start for JNLP files.

This issue is present in 6_18 and 6_19. It appears to be a regression, as there is no error with 6_16. I have not tested under 6_17.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I expect the application to launch normally
ACTUAL -
I receive a Java Web Start error dialog box.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
Contents of the "Launch File" tab
---------------------------------------------
<jnlp spec="1.0+" codebase="http://10.1.1.121:8080/DEV/"> <information> <title>Desktop Launcher</title> <vendor>Computer Projects of Illinois, Inc.</vendor> <homepage href="http://www.openfox.com"/> <description>OpenFox Desktop Launcher</description> </information> <security> <all-permissions/> </security> <update check="timeout" policy="always"/> <resources> <j2se version="1.5+"/> <jar download="eager" href="DesktopLauncher.jar"/> </resources> <application-desc main-class="DesktopLauncher"> <argument>-codebase http://10.1.1.121:8080/DEV/&lt;/argument> </application-desc></jnlp>


Contents of the "Exception" tab
---------------------------------------------
java.net.SocketException: Unexpected end of file from server
at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.HttpURLConnection.getResponseCode(Unknown Source)
at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
at com.sun.deploy.net.BasicHttpRequest.doGetRequestEX(Unknown Source)
at com.sun.deploy.net.DownloadEngine.isUpdateAvailable(Unknown Source)
at com.sun.deploy.net.DownloadEngine.isUpdateAvailable(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResource(Unknown Source)
at com.sun.javaws.LaunchDownload$DownloadTask.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)



REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
The work around is to either...
1) Have user clear Java temp files before each application launch
2) Have user uninstall Java and go back to 6_16

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