In log files of IT systems, there typically are three priority levels of interest for administrators:
INFO – Admins SHOULD know this (if they do not need to know this, it should not be shown by default).
WARNING – Something might lead to a problem, so admins MUST know this to be able to manage before something crashs.
ERROR – Something already broke, so admins MUST know this to fix it.
I wonder why the following line gets printed as WARNING in a fresh installation of GlassFish v3.1:
[#|2011-07-07T14:40:12.253+0200|WARNING|glassfish3.1|org.apache.catalina.connector.Request|_ThreadID=22;_ThreadName=Thread-1;|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|#]
What shall the administrator do now? Call Oracle? If the reaction is "ignore", then it is not worth getting printed.
So either this is a bug
hence this bug report and need to get fixed with high priority (if it wouldn't be high priority, it must not be WARNING, obviously) OR someone should rephrase that message in a way that makes the common administrator understand what to do now.
BTW, the message occurs after
and then logging into the admin console at http://localhost:4848 using IE9.