JDK-5006328 : winxp, java update fails because of file indexing system
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 1.4.1,1.4.2,1.4.2_01,5.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_2000,windows_xp
  • CPU: generic,x86
  • Submitted: 2004-03-02
  • Updated: 2013-06-04
  • Resolved: 2004-04-06
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
1.4.2_05 05Fixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Description
During the patching of java (which happens in every _0X release), we rename the target image to see if it is locked before patching.  Then we rename it again right before we patch.  However, the winxp file indexing system will sometimes keep the directory locked from the first rename.  If we take out the 2nd mv, the patcher will work and this problem will go away.

The customer Merck is requesting that we fix this as soon as possible.  We have also gotten quite a bit of feedback from consumers on this problem
###@###.### 2004-03-02

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_05 generic tiger-beta2 FIXED IN: 1.4.2_05 tiger-beta2 INTEGRATED IN: 1.4.2_05 tiger-b46 tiger-beta2
14-06-2004

WORK AROUND Right click on the drive selected for installation, and uncheck "allow indexing service to index this disk for fast file searching". 1.4.2_04 is currently the most recent 1.4.2 release available. 1.4.2_05 will be available soon. ###@###.### 2004-06-03
03-06-2004

EVALUATION committing to Tiger ###@###.### 2004-03-22 If you are seeing this bug with 1.4.2_05, please send us the $TEMP/java_install.log as well as the $SYSTEMDIR/jupdate*.log so we can debug. It may also be helpful if you create an msi log file. Instructions are at the bottom of: http://java.sun.com/j2se/1.4.2/docs/guide/plugin/developer_guide/silent.html ###@###.### 2004-06-01
01-06-2004

SUGGESTED FIX http://j2se.east/~billyh/merck/ ###@###.### 2004-03-02
02-03-2004