JDK-6710572 : PIP from 6u10 to 6u11 fails when jusched is running
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows,windows_xp
  • CPU: x86
  • Submitted: 2008-06-04
  • Updated: 2010-09-17
  • Resolved: 2008-10-01
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 b31Fixed 7Fixed
Related Reports
Duplicate :  
Duplicate :  
See the next note for updated information based on b27.

While testing the PIP for promoted build, I see the file mismatch error when patching from 6u11 to 6u12 if 6u5 is on the system.

The steps to reproduce the error 

1. Install 6u5
2. Install 6u10 jre
3. Install 6u11
4. Try to install 6u12,  You will get the file mismatch error complaining jusched.exe. Please see attached screen shot.

The 6u10 to 6u11 worked OK. The issue only happens for 6u11 to 6u12.

If I uninstall 6u5. Then everything works OK(6u10 to 6u11, 6u10 to 6u11 to 6u12, 6u10 to 6u12).
Updated with 2 scenarios for b27:
Scenario A:
1. Install 6u10 JRE.
2. Start jusched.exe.  Jusched will start when users reboot because it is in HKLM\Software\Microsoft\Windows\CurrentVersion\Run
3. Patch to 6u11.

Scenario B:
1. Install 6u5 or 6u6 JRE.
2. Install 6u10 JRE.
For some reason, installing 6u10 starts jusched when 6u5 or 6u6 is installed.
3. Patch to 6u11.

Actual behavior in both scenarios:
After installation of 6u11, the 6u10 version of jusched is running, until reboot and PendingFileRenameOperations applied to delete and replace jusched.exe.

The setup complete dialog says nothing about a reboot required (see attachment).

The PendingFileRenameOperations value is:
>reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" /v PendingFileRena
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
    PendingFileRenameOperations REG_MULTI_SZ          \??\C:\PROGRA~1\Java\jre6\bin\jusched.exe\0\0

If you try to install the b27 dummy 6u12 without reboot, "Error 25025.  A previous Java uninstallation was never completed.  You need to restart your computer before installing Java."  is displayed and the install is blocked.
6u12: http://j2se.east/arc/1.6.0_10/pit/2008-06-19.15_16/windows-i586/jre-6u12-windows-i586-p-iftw.exe

SUGGESTED FIX http://web-east.east.sun.com/www/webrevs/rkaja/6710572/ Rajani changed InstallExecuteSequence.idt so UnInstallJUpdate is run during remove or update.

EVALUATION jusched.exe is started by jre installation if it not the 1st jre on the system. -Rajani

EVALUATION I ran some more tests, and here is the behavior: Scenario 1: 1. Remove all JRE's 2. Installed 6u6 3. Checked tastmanager and jusched.exe isn't running 4. Install 6u10-b25 5. Checked tastmanager and jusched.exe *IS* running Scenario 2: 1. Remove all JRE's 2. Installed 6u10-b25 3. Checked tastmanager and jusched.exe *isn't* running This is inconsistent behavior. 6u10 kicks off jusched.exe immediately after installation *ONLY* if 6u5 is already installed.

EVALUATION The method that shutsdown the jusched.exe is invoked after patchjre is done. But patchjre is failing because jusched.exe is in use.