Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-ASCII characters are not saved correctly in JVM options added using the JVM Options page #24816

Closed
kaido207 opened this issue Feb 20, 2024 · 0 comments · Fixed by #24817
Closed

Comments

@kaido207
Copy link
Contributor

Environment Details

  • GlassFish Version (and build number): GlassFish 7.0.8
  • JDK version: OpenJDK version 11.0.12
  • OS: CentOS Linux release 7
  • Database: none

Problem Description

Non-ASCII characters are not saved correctly in JVM options added using the JVM Options page.

jvm_unicode1
jvm_unicode2

"-Dtest=あああ" is converted to "-Dtest=u3042u3042u3042", this is not expected behavior.

You can also confirm that it is not the expected JVM option value by using the asadmin command:

# /glassfish7/glassfish/bin/asadmin list-jvm-options
--add-opens=java.base/java.io=ALL-UNNAMED
:
-Xmx512m
-Dtest=u3042u3042u3042
-Dorg.glassfish.gmbal.no.multipleUpperBoundsException=true
:
-XX:NewRatio=2
Command list-jvm-options executed successfully.

Steps to reproduce

  1. access Admin Console.
  2. open Configulation > server-config > JVM Settings.
  3. open JVM Options.
  4. add the JVM option that contain Non-ASCII characters.
  5. save clicked.

Impact of Issue

Users cannot create JVM options that contain Non-ASCII characters in Admin GUI, such as directory paths.

arjantijms added a commit that referenced this issue Feb 20, 2024
Fixes #24816 Non-ASCII characters are not saved correctly in JVM options added using the JVM Options page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant