[
https://issues.jboss.org/browse/WFLY-3723?page=com.atlassian.jira.plugin....
]
Romain Pelisse commented on WFLY-3723:
--------------------------------------
Ok, switching to ROOT has not fix the issue, because when we request for the locale
"en_US" we still end up in the same pitfall - there is no bundle for it. I have
a fix however, that simply test if language is 'en' and if so, switch to
"ROOT".
setting the local to english in CLI commands on non-english systems
does not produce english output
---------------------------------------------------------------------------------------------------
Key: WFLY-3723
URL:
https://issues.jboss.org/browse/WFLY-3723
Project: WildFly
Issue Type: Bug
Components: Localization
Affects Versions: 8.1.0.Final
Environment: Tested on MacOS running in German
Reporter: Tom Fonteyne
Assignee: Romain Pelisse
Priority: Minor
A German (or french etc...) system must be used to reproduce.
It is likely this is not limited to MacOS, but I do not have a non-english Linux system
available
An out of the box install of wildfly/EAP:
Without configuration, the log file is in German as expected.
Using these CLI comands:
:read-operation-description(name=stop-servers,locale=de_DE) -> german
:read-operation-description(name=stop-servers,locale=en_US) -> german
:read-operation-description(name=stop-servers,locale=fr_FR) -> french
So we cannot get the CLI to produce english output
when configuring JAVA_OPTS in domain.conf with:
JAVA_OPTS="$JAVA_OPTS -Duser.language=en -Duser.country=DE -Duser.encoding=utf-8
The log is now in English -> works as expected; and:
:read-operation-description(name=stop-servers,locale=de_DE) -> german
:read-operation-description(name=stop-servers,locale=en_US) -> english
So it seems we have a bug where the locale set to start the domain takes precedence over
the locale set in the CLI command (but only when English is asked)
I presume this is because English is the default locale.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)