Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8242283

Can't start JVM when java home path includes non-ASCII character

    XMLWordPrintable

Details

    • b19
    • x86_64
    • windows_10
    • Not verified

    Backports

      Description

        Java fails to start on Windows 10 with non-ASCII characters in the path if current regional format differs from the system locale.
        (Settings | Time & Language | Language | Administrative language settings | Administrative tab | Language for non-Unicode programs | System locale: X)
        (Settings | Time & Language | Regional format | Current format: Y)

        For example, jdk15 fails if java path contains German characters and:

        System locale: German (Germany)
        Current format: English (Europe)
        Region: Germany
        Active code page: 850

        > C:\qwertz-ßüöä\openjdk-15-ea+17_windows-x64\bin\java -version
        Error occurred during initialization of VM
        Failed setting boot class path.

        Previous jdk versions work ok in this case:

        > C:\qwertz-ßüöä\openjdk-11+28_windows-x64\bin\java -version
        openjdk version "11" 2018-09-25
        OpenJDK Runtime Environment 18.9 (build 11+28)
        OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)

        > C:\qwertz-ßüöä\openjdk-13+33_windows-x64\bin\java -version
        openjdk version "13" 2019-09-17
        OpenJDK Runtime Environment (build 13+33)
        OpenJDK 64-Bit Server VM (build 13+33, mixed mode, sharing)

        > C:\qwertz-ßüöä\openjdk-14+36_windows-x64\bin\java -version
        openjdk version "14" 2020-03-17
        OpenJDK Runtime Environment (build 14+36-1461)
        OpenJDK 64-Bit Server VM (build 14+36-1461, mixed mode, sharing)

        Jdk15 and jdk14 fail if java path contains Russian characters and:

        System locale: Russian (Russia)
        Current format: English (Europe)
        Region: Russia
        Active code page: 866

        > C:\йцукен\openjdk-15-ea+17_windows-x64\bin\java -version
        Error occurred during initialization of VM
        Failed setting boot class path.

        > C:\йцукен\openjdk-14+36_windows-x64\bin\java -version
        Error occurred during initialization of VM
        Failed setting boot class path.

        Old jdk13 and jdk11 versions work ok:

        > C:\йцукен\openjdk-11+28_windows-x64\bin\java -version
        openjdk version "11" 2018-09-25
        OpenJDK Runtime Environment 18.9 (build 11+28)
        OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode)

        > C:\йцукен\openjdk-13+33_windows-x64\bin\java -version
        openjdk version "13" 2019-09-17
        OpenJDK Runtime Environment (build 13+33)
        OpenJDK 64-Bit Server VM (build 13+33, mixed mode, sharing)

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8245390 Can't start JVM when java home path includes non-ASCII character

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8246680 Can't start JVM when java home path includes non-ASCII character

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8247627 Can't start JVM when java home path includes non-ASCII character

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8261653 Can't start JVM when java home path includes non-ASCII character

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8276221 Can't start JVM when java home path includes non-ASCII character

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8245223 Can't start JVM when java home path includes non-ASCII character

            • P3 - Major loss of function.
            • Closed
            duplicates

            Bug - A problem which impairs or prevents the functions of the product. JDK-8242608 java.exe does not start with special characters in parent directory names

            • P3 - Major loss of function.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8241461 Can't start JVM when java path includes CJK chars and code-page is English

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. JDK-8191521 handle long relative path specified in -Xbootclasspath/a on windows

            • P3 - Major loss of function.
            • Resolved

            Bug - A problem which impairs or prevents the functions of the product. JDK-8240197 Cannot start JVM when $JAVA_HOME includes CJK characters

            • P3 - Major loss of function.
            • Resolved

            Bug - A problem which impairs or prevents the functions of the product. JDK-8242608 java.exe does not start with special characters in parent directory names

            • P3 - Major loss of function.
            • Closed
            links to

            Commit Commit openjdk/jdk13u-dev/c229f3c9

            Review Review openjdk/jdk13u-dev/120

            Activity

              People

                ysuenaga Yasumasa Suenaga
                vprovodin Vitaly Provodin
                Votes:
                0 Vote for this issue
                Watchers:
                17 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: