Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.213.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1336577365.48091.YahooMailNeo@web29602.mail.ird.yahoo.com>
References: <1336572438.67242.YahooMailNeo@web29604.mail.ird.yahoo.com>
	<1336573518.38831.YahooMailNeo@web29605.mail.ird.yahoo.com>
	<4FAA869F.3070902@ice-sa.com>
	<1336577365.48091.YahooMailNeo@web29602.mail.ird.yahoo.com>
Date: Thu, 10 May 2012 15:31:34 +0400
Message-ID: 
 <CABzHfVkO8tUEPKJhd5AAxsEjaXyNfA4f98ng_wNTVXBdf3ToZw@mail.gmail.com>
Subject: Re: tomcat pausing and process killed
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

2012/5/9 Miguel Gonzalez <miguel_3_gonzalez@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org