(Note that may apply to other releases, vkak has not verified this in versions other then 4.3.0_CP04, which is what the customer is running.)

-------------
Customer:
-------------

"We ran into a problem that after HttpServletResponse#reset was called, any subsequent response.setContentType or response.setCharacterEncoding calls had not effect on changing the content type. And on further investigation, it was found to be a Tomcat issue that was reported and fixed as below:

https://issues.apache.org/bugzilla/show_bug.cgi?id=43236

Apparently the fix is not in the JBoss 4.3.0 GA release (no cp). Is the fix included in any 4.3.0 cp release? Thanks."

-------------
From vkak:
-------------

"Jboss4.3.0 contains JbossWeb 2.0.0 which is based on 6.0.13 as explained over here
http://www.jboss.org/community/docs/DOC-12545

The fix does not appear in
http://anonsvn.jboss.org/repos/jbossweb/branches/JBOSSWEB_2_0_0_GA_CP/src/share/classes/org/apache/catalina/connector/Response.java
http://anonsvn.jboss.org/repos/jbossweb/branches/2.0.x/src/share/classes/org/apache/catalina/connector/Response.java

Also the fix does not appear in tomcat 6.0.13

http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_13/java/org/apache/catalina/connector/Response.java

The fix is done in tomcat6.0.16 +
http://svn.apache.org/repos/asf/tomcat/tc6.0.x/tags/TOMCAT_6_0_16/java/org/apache/catalina/connector/Response.java

So JbossEAP version 4.3.0 is not containing the fix for the following bugzilla issue
https://issues.apache.org/bugzilla/show_bug.cgi?id=43236

Regards,
Vicky"