JDK-6626922 : PIP breaks if processes that lock Java are opened after FileInUse detection, but before patching
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2007-11-07
  • Updated: 2010-09-08
  • Resolved: 2008-03-14
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
6u10 b13Fixed
Related Reports
Relates :  
JDK-6593761 - patch-in-place breaks if previous JRE image has locked files.
Description
On Windows Vista..

 * Install 6u5
 * Launch IE (no applets)
 * Install 6u6 iftw
 * Installer prompts that IE is open
 * Close IE and continue with installation
 * When installer shows the license screen, launch IE again

If installer doesn't detect IE is launched during installation bug is
reproduced. After this version of jqs_plugin.dll and ssv.dll still shows
6.0.50.407. This scenario works fine on WinXP.
Comments
SUGGESTED FIX Moved the "Close Applications" dialog from the online install to the Install UI Sequence for all installs. It will appear after the Custom Setup / Change Folder dialog when we know what the installation directory is and immediately before the Setup Progress dialog. For PatchInPlace, there is no user interaction between the new location of the Close Applications dialog and the patching of files. Having this logic in all Install UI sequences may detect some in use conditions that were previously reported as 1722 errors. webrev: http://sa.sfbay.sun.com/projects/deployment_data/6u10/6626922.1
13-02-2008
EVALUATION Right now the FilesInUse dialog is only part of the iftw.exe. It should also be part of the MSI process. I think the correct fix would be to share this code between the jinstall and RegUtilsMSI.dll. We need it for jinstall, for when java update needs the functions to detect if the jre-image is locked. We really should be showing the FilesInUse dialog right before the patchjre.exe customaction runs.
13-11-2007