Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: EE-3.3.0.GA_P03
-
Fix Version/s: EE-3.3.0.GA_P03
-
Component/s: Sample Apps
-
Labels:None
-
Environment:Glassfish 3.1.2.2 on amazon AWS, ICEfaces EE-3.3.0.GA_P03 Jenkins build 04.
-
Assignee Priority:P2
Description
Server warning seen when using sample apps on glassfish 3.1.2.2. This warning is constantly being displayed while interacting with auction and once or twice when using a scopes application .
[#|2015-05-01T17:03:27.692-0400|WARNING|glassfish3.1.2|org.apache.catalina.connector.Request|_ThreadID=80;_ThreadName=http-thread-pool-8080(2);|PWC4011: Unable to set request character encoding to UTF-8 from context /auction, because request parameters have already been read, or ServletRequest.getReader() has already been called|#]
[#|2015-05-01T17:03:27.692-0400|WARNING|glassfish3.1.2|org.apache.catalina.connector.Request|_ThreadID=80;_ThreadName=http-thread-pool-8080(2);|PWC4011: Unable to set request character encoding to UTF-8 from context /auction, because request parameters have already been read, or ServletRequest.getReader() has already been called|#]
This seems to be a well known issue occurring in Glassfish 3.1.2.
The following links explain why this happens and the workarounds:
http://stackoverflow.com/questions/7643484/how-to-get-rid-of-warning-pwc4011-unable-to-set-request-character-encoding-to
http://qussay.com/2011/07/11/solving-pwc4011-unable-to-set-request-character-encoding-to-utf8/
Modifying our code to workaround this limitation would be quite extensive.