This is not a bug in JBoss. This is related to the way of handling charcters encoding in Servlet and JSP. Your application works in WAS, because WAS has implemented its own way of handling characters in HTML request.

Problem 1: When a form is submitted, the browser will encode the characters in the character encoding set in the browser at that moment. The default encoding is the encoding at which the page is displayed but this can be changed by the user easily.

Problem 2: When the Servlet container receives the request, it always pass the request parameters to your program decoded in ISO-8859-1 encoding. (e.g. Browser encoded in UTF-8 but container decoded in ISO-8859-1.) Thus your servlet or JSP will always receive garbage for characters other than ISO-8859-1 encoding.

To solve problem 1, you have to add the accept-encoding option in the html form tag

<form action="abc.do" method="post" accept-encoding="UTF-8">

<html:form action="abc" accept-charset="UTF-8">

String value = request.getParameter("mytext");
try{
 value = new String(value.getBytes("8859_1"), "UTF-8");
}catch(java.io.UnsupportedEncodingException e){
 System.err.println(e);
}

<!-- This filter should be placed at beginning of web.xml so that the request is not accessed yet -->
<filter>
 <display-name>set character encoding</display-name>
 <filter-name>setCharacterEncodingFilter</filter-name>
 <filter-class>your.package.web.filter.SetCharacterEncodingFilter</filter-class>
 <init-param>
 <param-name>encoding</param-name>
 <param-value>UTF-8</param-value>
 </init-param>
</filter>

<filter-mapping>
 <filter-name>setCharacterEncodingFilter</filter-name>
 <url-pattern>/*</url-pattern>
</filter-mapping>

package your.package.web.filter;

import java.io.IOException;
import javax.servlet.*;
import javax.servlet.http.*;

/**
 * Set the character encoding of the request to as set in "encoding"
 * this should be done before the request is accessed.
 */
public class SetCharacterEncodingFilter implements Filter {

 private FilterConfig filterConfig;
 private String encoding;

 public void init(FilterConfig filterConfig) {
 this.filterConfig = filterConfig;
 this.encoding = filterConfig.getInitParameter("encoding");
 }
 public void doFilter(ServletRequest request,
 ServletResponse response,
 FilterChain chain) throws IOException, ServletException {
 request.setCharacterEncoding(this.encoding);
 chain.doFilter(request, response);
 }
 public void destroy() {
 this.filterConfig = null;
 }
}

I'm having the same problem with my application (I use latin characters, ISO8859-15). But the weird thing is that my windows installation seems to have no problem. The same version of JBoss on both machines, but my test server is a RedHat AS. In linux, JBoss seems to be re-encoding the UTF-8 string passed by the client again to UTF-8. Is there a way to prevent this without using the filter? I installed a tomcat 5.5 on that server and that installation seems to have no problem at all.

try with below link

http://allinoneissues.blogspot.jp/2012/05/german-characters-encoding-issue.html