FULL PRODUCT VERSION :
java version "1.6.0-rc"
Java(TM) SE Runtime Environment (build 1.6.0-rc-b99)
Java HotSpot(TM) Client VM (build 1.6.0-rc-b99, mixed mode, sharing)
FULL OS VERSION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
The .jar file which launches at double click doesn't launch if the path to it contains cyrilic letters. A path with cyrilic letters makes the .jar file fail at start, it says "Fatal exception occured. Program will exit", the title is "Java Virtual Machine Launcher".
When I put the file at "C:\orders\RotoComplectNT.jar" the same file (RotoComplectNT.jar) starts and works fine.
All files were compiled with the jdk4 (to ensure the app will run on 4 and above) and tested with jdk6 beta 99.
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Did not try
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Did not try
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
The only step to reproduce it is to make the path to any .jar file to contain cyrilic letters.
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.6.0-rc"
Java(TM) SE Runtime Environment (build 1.6.0-rc-b99)
Java HotSpot(TM) Client VM (build 1.6.0-rc-b99, mixed mode, sharing)
FULL OS VERSION :
Microsoft Windows XP [Version 5.1.2600]
A DESCRIPTION OF THE PROBLEM :
The .jar file which launches at double click doesn't launch if the path to it contains cyrilic letters. A path with cyrilic letters makes the .jar file fail at start, it says "Fatal exception occured. Program will exit", the title is "Java Virtual Machine Launcher".
When I put the file at "C:\orders\RotoComplectNT.jar" the same file (RotoComplectNT.jar) starts and works fine.
All files were compiled with the jdk4 (to ensure the app will run on 4 and above) and tested with jdk6 beta 99.
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Did not try
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Did not try
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
The only step to reproduce it is to make the path to any .jar file to contain cyrilic letters.
REPRODUCIBILITY :
This bug can be reproduced always.
- relates to
-
JDK-4858889 JNI Invocation API strings not UTF-8
- Closed
-
JDK-4904545 JDK tools fail to work with non-latin characters in the install path
- Closed
-
JDK-6937897 (jli) The "-javaagent" option cannot decode the given path correctly
- Closed