users@glassfish.java.net

Re: server.log filled with irritating "unable to set request character encoding to UTF-8" errors

From: Jan Luehe <Jan.Luehe_at_Sun.COM>
Date: Wed, 26 Nov 2008 08:30:31 -0800

Hi Dick,

On 11/26/08 03:08 AM, Dick Davies wrote:
> Does anyone have a fix for this? We run Roller, but I've seen it with
> WebSynergy (and Liferay ) too:
>
> [#|2008-11-26T11:05:03.070+0000|WARNING|sun-appserver9.1|org.apache.coyote.tomcat5.CoyoteRequest|_ThreadID=34;_ThreadName=httpSSLWorkerThread-38181-7;_RequestID=638142a3-30f9-4614-9b70-e8611935d5b6;|PWC4011:
> Unable to set request character encoding to UTF-8 from context ,
> because request parameters have already been read, or
> ServletRequest.getReader() has already been called|#]
>
> [#|2008-11-26T11:05:04.470+0000|WARNING|sun-appserver9.1|org.apache.coyote.tomcat5.CoyoteRequest|_ThreadID=25;_ThreadName=httpSSLWorkerThread-38080-13;_RequestID=176f3e3c-5765-4e6d-af13-13d88a03b049;|PWC4011:
> Unable to set request character encoding to UTF-8 from context ,
> because request parameters have already been read, or
> ServletRequest.getReader() has already been called|#]
>
> [#|2008-11-26T11:05:08.070+0000|WARNING|sun-appserver9.1|org.apache.coyote.tomcat5.CoyoteRequest|_ThreadID=36;_ThreadName=httpSSLWorkerThread-38181-6;_RequestID=411715a7-666b-49d0-91c8-2562d1fdee22;|PWC4011:
> Unable to set request character encoding to UTF-8 from context ,
> because request parameters have already been read, or
> ServletRequest.getReader() has already been called|#]
>
> Any ideas?
>
> ( I'm not really clear why "org.apache.coyote.tomcat5.CoyoteRequest"
> is there at all; I thought we were using Grizzly)
>

CoyoteRequest is a wrapper around the underlying Grizzly request.

See

  
http://wiki.glassfish.java.net/Wiki.jsp?page=FaqWebAppUnableToSetRequestCharEncoding

for an explanation of the warning.

Hope this helps.

Jan