Name: rmT116609 Date: 08/11/2003
FULL PRODUCT VERSION :
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
FULL OS VERSION :
Microsoft Windows XP [Version 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
System Locale: "en-ca"
Japanese support is installed.
A DESCRIPTION OF THE PROBLEM :
The os must be set to any english locale and the japanese support must be installed on the system.
If a Japanese (or any non-"windows-1252") charcters are used in the install path the JDK, the tools fail tu run returning the folwoing error:
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
The same error occurs if JDK is installed in a directory with only latin characters in the path, and java.exe is used to run a class with a japanese character in the path.
The problem occurs because JVM uses system IO functions that work only with the file names containing system encoding (in this case "windows-1252") characters.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
The os must be set to any english locale and the japanese support must be installed on the system.
Install JDK into the default directory "C:\j2sdk1.4.2". Rename the directory to
"C:\j2sdk1.4.2�N", where the last character is any japanese cahracter. Then try to run any tool from "C:\j2sdk1.4.2�N\bin" directory.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The expected result is the tools must work even if I use in the paths characters other than the ones supported by the system's default encoding.
ACTUAL -
The tools fial to run.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
If one wishes to use Japanese characters in directory names, then he must set his system locale to Japanese, for chinese characters - system locale to chinese, etc.
(Incident Review ID: 198691)
======================================================================
FULL PRODUCT VERSION :
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
FULL OS VERSION :
Microsoft Windows XP [Version 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
System Locale: "en-ca"
Japanese support is installed.
A DESCRIPTION OF THE PROBLEM :
The os must be set to any english locale and the japanese support must be installed on the system.
If a Japanese (or any non-"windows-1252") charcters are used in the install path the JDK, the tools fail tu run returning the folwoing error:
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
The same error occurs if JDK is installed in a directory with only latin characters in the path, and java.exe is used to run a class with a japanese character in the path.
The problem occurs because JVM uses system IO functions that work only with the file names containing system encoding (in this case "windows-1252") characters.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
The os must be set to any english locale and the japanese support must be installed on the system.
Install JDK into the default directory "C:\j2sdk1.4.2". Rename the directory to
"C:\j2sdk1.4.2�N", where the last character is any japanese cahracter. Then try to run any tool from "C:\j2sdk1.4.2�N\bin" directory.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The expected result is the tools must work even if I use in the paths characters other than the ones supported by the system's default encoding.
ACTUAL -
The tools fial to run.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
If one wishes to use Japanese characters in directory names, then he must set his system locale to Japanese, for chinese characters - system locale to chinese, etc.
(Incident Review ID: 198691)
======================================================================
- duplicates
-
JDK-6807481 JVM fails to find JNI DLL in a folder with Unicode chars
- Closed
- relates to
-
JDK-6475368 Jar file doesnt execute if the path to it contains cyrilic letters
- Resolved
-
JDK-6582455 java throws NoClassDefFoundError when user.dir includes non-ascii characters
- Closed
-
JDK-4900150 Use Unicode API on in the area other than AWT
- Open
-
JDK-4858889 JNI Invocation API strings not UTF-8
- Closed