JDK-6898437 : Java Web Start 6 does not return appropriate exit code upon failure
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6u16
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp,windows_vista
  • CPU: x86
  • Submitted: 2009-11-05
  • Updated: 2010-12-04
  • Resolved: 2010-08-03
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.
JDK 6 JDK 7
6u21-rev b08Fixed 7Fixed
Related Reports
Duplicate :  
JDK-6899348 - Java Web Start to return error code reflecting reason of failure
Relates :  
JDK-6966402 - Request to localise two strings in deployment code
Description
Java Web Start 1.4.2 returned "-1", when an error was encountered
during download or application start of a Java Web Start application. 
Otherwise, if everything went fine, "0" was returned.

Java Web Start 6 always returns "0", no matter, if there was a 
problem encountered during download or application start or not.
Comments
SUGGESTED FIX two error returns call Main.systemExit(0). 1.) in Main.java, when importing with cache disabled, the other 2.) in LaunchErrorDialog, if exit flag specified both need to be changed to SystemExit(-1) to provide this compatibility.
15-03-2010
EVALUATION This usage of the private interface between javaws.exe and com.sun.javaws.Main is usage of a private interface and completely unsupported. Although I agree we should make the change suggested in an update release, even making this change could be considered a regression from 1.5.0 and earlier jdk6 updates. I do not see this qualifys as a show-stopper for 6u18, and am reprioritizing as P3.
01-12-2009
EVALUATION Anytime JWS6 encounters a launch issue - it exits with code of 0. This is different behaviour to 1.4.2 JWS and should be corrected. We should indicate errors with exit code of -1.
20-11-2009
WORK AROUND Use JNLP DownloadService API to perform the JARs download instead, which will throw exception if download fails ?
05-11-2009
EVALUATION I don't think we docuemented on the usage of javaws return value. It's never a supported/tested feature. we should investigate this for 6u20.
05-11-2009