JDK-6627643 : installer PIP should warn user if kernel isn't finished downloading/reconstructing
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2007-11-08
  • Updated: 2010-09-17
  • Resolved: 2008-08-29
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.
6u10 b22Fixed 7Fixed
Steps to reproduce:

1. Install 6u10 kernel
2. Launch 6u11 before 6u10 kernel is finished downloading/reconstructing
3. 6u11 installer will get error when patching

Expected behavior:

6u11 installer should tell the user that the previous jre image isn't finished downloading/reconstructing.  We should consult UE/docs to find the correct message wording.

EVALUATION The logic outlined in the wiki is currently under web review. Additionally, a similar call to the logic is made BEFORE the FilesInUse dialog. However, when calling before FIU, the Kernel finalization is averted. With this additional call, we also safeguard against killing any kernel download that is in progress via FilesInUse. By implementing the fix in this way, we have also added a valuable feature to the PIP installer: if the user has not run java since the previous kernel installation OR encountered an error during a prior finalization, the PIP will function to finalize OR re-finalize and/or clean up prior finalization attempts. For example, if windows explorer happens to have %PROGFILES%\Java\jre6\lib\bundles locked, and java is run to finalize the kernel, an error will be thrown, and %PROGFILES%\Java\jre6\lib\bundles will not be cleaned off the system. When the PIP installer is run after this scenario, the kernel finalization will be "re-kicked" and the runtime image cleaned up...all 'under the hood'.

EVALUATION Please x-ref the following wiki: http://j2se.sfbay.sun.com/web/bin/view/Deployment/KernelCompletionPIP