JDK-6906351 : Offline Application Start does not work.Regression from 6u18 b04
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6u18
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2009-12-02
  • Updated: 2011-02-16
  • Resolved: 2010-01-13
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.
6u18 b06Fixed
Related Reports
Relates :  
Relates :  
Relates :  
The fix for 6800992 is integrated in 6u18 b03.
Testcase: http://web-east.east.sun.com/www/tests/1.6.0_18/6800992/test.html

With 6u18 b03 
The test is working fine for windows.During PIT time iteslf 
offline launch was not working on solaris.(Filed 6888510)

With b04 
javaws http://javafx.com/samples/BrickBreaker/webstart/BrickBreaker.jnlp
is not launching offline.The error is  unknown host:javafx.com
javaws http://web-east.east.sun.com/www/tests/1.6.0_18/6800992/draw.jnlp
is launching fine

With b05
both these jnlps are not launching offline because of unknown host exception
(Screen shots attached)

EVALUATION With the performance code refactoring, JARs update check are now only done via Launcher.downloadResources. In case that we are disconnected from the network and update check causes IOException, we should check to see if JNLP allows offline and whether all resource are cached already. If so, continue to launch using cached resource.

EVALUATION this affects webstart applications started via desktop shortcut as well. with this bug, when application is cached and machine is offline, it will fail because of this bug. when we do update check for JARs, if JNLP file allow-offline, we should continue to launch using cached resource if available.