JDK-7098160 : Launch from cache (background update check) => expect 0 network request on critical path
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-10-05
  • Updated: 2013-12-06
  • Resolved: 2011-10-28
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.
7u2Fixed 8 b12Fixed
Launching application from cache may cause update check request when jar is opened by DeployCacheHandler.
This may cause robustness problems as jar might be updated and do not much "cached" data we used to decide about permissions, etc.
It also cause significant slow down if there are no updates.

Verified fix using b118

EVALUATION The idea of the fix is to save set of URLs to be updated in background and do not try to update them if they are used earlier. Refactored update tracking a little into separate class.