-
Bug
-
Resolution: Fixed
-
P2
-
6u10
-
b26
-
x86
-
windows_xp
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2199278 | 7 | Paul Klingaman | P2 | Closed | Fixed | b64 |
Real-world scenario:
- Install 6u10 to the default directory, "C:\Program Files\Java\jre6\".
- From the command line, run a jar file using "C:\program files\java\jre6\bin\java.exe" (all lower case). Leave it running.
- Install 6u11 online installer to patch 6u10 at "C:\Program Files\Java\jre6\".
"C:\program files\java\jre6\bin\java.exe" is in use.
but not displayed in the FilesInUse dialog box.
The check against the directory 6u11 is being installed to is using StrStr() which is case-sensitive.
- Install 6u10 to the default directory, "C:\Program Files\Java\jre6\".
- From the command line, run a jar file using "C:\program files\java\jre6\bin\java.exe" (all lower case). Leave it running.
- Install 6u11 online installer to patch 6u10 at "C:\Program Files\Java\jre6\".
"C:\program files\java\jre6\bin\java.exe" is in use.
but not displayed in the FilesInUse dialog box.
The check against the directory 6u11 is being installed to is using StrStr() which is case-sensitive.
- backported by
-
JDK-2199278 FilesInUse not detecting executables when path differs in case
- Closed
- relates to
-
JDK-6661934 Files In Use does not find processes started with a short path
- Closed