jboss 5.1 encoding problem

[yves.benigot]

we install jboss 5.1.0-GA and start the default server without any modification

if we hit the error page, for example with http://10.1.1.5:8080/xxx we have a page with incorrect encoding (under firefox 3.5) :
type Rapport d'�tat
message /xxx
description La ressource demand�e (/xxx) n'est pas disponible.


of course if we install real jboss applications we have a lot of problems with webapps which dont deploy and so on

our setup :
Jboss 5.1.0 GA
Redhat ES 4
Java 5.0.19
LANG=fr_FR.UTF-8

we see the same problems under windows

any idea ?

[jaikiran]

"yves.benigot" wrote:

of course if we install real jboss applications we have a lot of problems with webapps which dont deploy and so on

Which real applications? And what errors do you see. There was a thread in this forum about something similar, just want to make sure if this is the same issue

[yves.benigot]

The encoding problem on the error page remains even if we start the server right after installing the archive.

On the deployment problems we have progressed, and the situation is that we have to correct some configuration files and JSP where jboss 5 is stricter.

More information:
- we see encoding errors in the error page, but also in the logs
- we have 15 war and 2 ear in a directory named deploy/ginerativ,
and 6 sar files
- libraries 36 of them (10 of them are developped in house) in lib/ginerativ
(we use subdirectories to avoid merging our files with jboss installed files)

On the same server, with the same java and envrionment setup, and jboss 4.2.3, the error page is properly encoded with french accents.

Also we found that, for the moment, the server is slower than jboss 4.2.3, although this seems an unlikely explanation.

[wolfgangknauf]

Hi Yves,

please check the following:
-is the "pageEncoding" attribute of the "@page" directive of your errorpage set and matches the "real" file encoding?
-is the "contentType" attribute of the "@page" directive of your errorpage set and matches the target HTML content type?

<%@page language="java"
 contentType="text/html; charset=windows-1252"
 pageEncoding="windows-1252"%>

-does the "Content-Type" of meta tag match all those encodings?

 <meta http-equiv="Content-Type" content="text/html; charset=windows-1252" />

If all those are valid and there is no encoding changed in some server config, then the errorpage should work.

Best regards

Wolfgang