JDK-5075953 : RapidUpdateCheck returns completed when resource not there.
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2004-07-20
  • Updated: 2006-01-13
  • Resolved: 2004-09-15
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.
Other JDK 6
5.0u8Fixed 6 mustangFixed
Description
When going thru the check for update, if <offline-allowed> is specified then the process quickly times out and proceeds with the cached version.
If <offline-allowed> is not present it will not return untill every resource has been checked.  Unfortunately if the check returns an Exception (like not found) the code returns as if the check showed that there is no update.
Removing a resource from the web is updating it, and should in this case not launch the app.  
When a resource isn't there, we should treat it as updated, and prevent launching.
Comments
EVALUATION This problem still exists in tiger. If the connection to a host is broken, and an application has an href, but does not include offline-allowed, then the cached application can still run in tiger.
13-01-2006
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mustang FIXED IN: mustang INTEGRATED IN: mustang
15-09-2004
PUBLIC COMMENTS programs w/o <offline-allowed> shouldn't launch unless the check for update can be completed.
15-09-2004
EVALUATION if not offline-allowed, dont't launch without completeing update check. ###@###.### 2004-07-20
20-07-2004