3 Replies Latest reply on Jul 16, 2010 4:26 PM by frankgrimes97

JBoss ignoring LOCALE and LC_CTYPE when determining file.encoding

frankgrimes97 Jun 23, 2010 1:17 PM

Hi All,

We're in the process of migrating one of our applications which runs on JBoss 4.0.5.GA from a SuSE 9 to a SuSE 10 server and have encountered the following problem.

On the new SuSE10 server, despite the fact that LOCALE and LC_CTYPE are both set to "en_US.utf8" the JBoss boot.log shows file.encoding to be "ANSI_X3.4-1968".

The old SuSE9 server shows file.encoding to be "UTF-8".

To see if it might be a JVM/OS issue, I wrote a standalone application which prints the value of the file.encoding system property and it correctly shows "UTF-8" on *both* servers.

Why would it work in a standalone test case and not when launching JBoss?

Is its shell script doing something to cause LOCALE and LC_CTYPE to not be read correctly in this environment?

Note that I am launching JBoss using the same user that I use to launch my standalone test case.

In searching the forums I found the following old post with no resolution: http://community.jboss.org/message/187687

Any help/ideas would be much appreciated.

Regards,

Frank Grimes

1. Re: JBoss ignoring LOCALE and LC_CTYPE when determining file.encoding

frankgrimes97 Jul 14, 2010 2:39 PM (in response to frankgrimes97)

Does nobody have any suggestions for what might be going wrong here?
Actions
2. Re: JBoss ignoring LOCALE and LC_CTYPE when determining file.encoding

jaikiran Jul 16, 2010 5:00 AM (in response to frankgrimes97)
Have you tried setting

-Dfile.encoding=UTF-8

in the JAVA_OPTS section of run.conf? Can you post your boot.log (not server.log)?
Actions
3. Re: JBoss ignoring LOCALE and LC_CTYPE when determining file.encoding

frankgrimes97 Jul 16, 2010 4:26 PM (in response to jaikiran)

Adding -Dfile.encoding explicitly to the startup script resolves the issue.

I guess we'll need to do that moving forward instead of relying on the host's environment variables.
Still, it's very odd that a standalone command-line test application sets the file.encoding correctly based on LOCALE/LC_CTYPE.
Actions

Go to original post