In both JIRA test and production servers we have "Description" field set to "Wiki Style Renderer". However in test server (v6.3.11) the text displays correctly, e.g.,
Add the “Predefined Message Truncated” alert message box
In production server (v6.3.15) the text displays incorrectly, e.g.,
Add the ���Predefined Message Truncated��� alert message box
Not sure why? Is there a setting in JIRA that I need to change?
Thanks for your input.
Check if in the one that it's working, you have not set the collation in the JVM arguments. It's possible that the problem is related to this. Other option is a misconfiguration in the proxy (if you are using one).
-- Pedro
We did not set collation in the JVM arguments and there is no proxy setting for our servers. However the test server has Red Hat Enterprise Linux but the prod server has CentOS. No sure if the two have anything to do with collation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The test server MySQL jiradb database has the following character set setting: +--------------------------+----------------------------+ | Variable_name | Value | +--------------------------+----------------------------+ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | utf8 | | character_set_filesystem | binary | | character_set_results | latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | +--------------------------+----------------------------+ While the prod server MySQL jiradb database has the following character set setting: +--------------------------+----------------------------+ | Variable_name | Value | +--------------------------+----------------------------+ | character_set_client | utf8 | | character_set_connection | utf8 | | character_set_database | utf8 | | character_set_filesystem | binary | | character_set_results | utf8 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | +--------------------------+----------------------------+ Does anyone know this might be the root cause?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.