2012/5/9 Miguel Gonzalez <miguel_3_gonza...@yahoo.es>: > > I have tomcat 5.5.27 and jdk 1.5.0_17 > (..) > > May 8, 2012 12:03:48 PM org.apache.tomcat.util.http.Parameters > processParameters > WARNING: Parameters: Character decoding failed. Parameter skipped. > >(...) > > I will check it, however I don't see in the access logs something relevant. > Any string I can check or status code?
1. Requests that are rejected early (that is before they reach a Valve) would not be logged by AccessLogValve in any Tomcat 5.5.x version. This issue was fixed ~1,5 years ago in 6.0 and 7.0 only. Thus to see all received requests you need to have an up-to-date version of Tomcat 6 or 7. 2. When "invalid chunk" error is detected during parameter parsing, the bad parameter is just ignored as if it never existed in the query string. It does not cause request to fail, because Servlet API methods such as request.getParameter() do not support error reporting. They cannot throw exceptions and they cannot change the response. What your code does when a parameter is missing is up to your code. Your stacktrace mentions "FastCommonAccessLogValve" so this request should be mentioned in the access log. > memory use increases just before the system crashed. Maybe some bot is walking around your server, and that causes creation of new session for each request? Maybe your web site is popular in certain hours and cannot withstand the load? Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
