[JSPWIKI-320] glassfish reports setting character encoding too late in the request response cycle

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.6.2
• Fix Version/s: 2.7.x
• Component/s: Servlet Container/Java compatibility

Environment

glassfish, fedora, sun jre 1.6

• Assignee: Harry Metske
• Reporter: Clay Atkins
• Created: 27/Jul/08 16:39
• Updated: 15/Nov/21 13:49
• Resolved: 10/Aug/08 12:04

Description

See this error in glassfish logs for nearly every request:

[#|2008-07-27T11:33:01.687-0500|WARNING|sun-appserver9.1|org.apache.coyote.tomca
t5.CoyoteRequest|_ThreadID=31;_ThreadName=httpSSLWorkerThread-443-6;_RequestID=f
e1c5e05-09e8-4b21-a9eb-c9eebc59c689;|PWC4011: Unable to set request character en
coding to UTF-8 from context /ewiki, because request parameters have already bee
n read, or ServletRequest.getReader() has already been called|#]

You have to set the character encoding before manipulating output.