No without wild guessing: AjpProcessor.recycle() now nulls input. On the next loop through processing the connection, trying to read from the nulled input will lead to an NPE, producing the 400 log entry.
In 7.0.16 recycle was implemented in AbstractAjpProcessor.java and did not null input. Regards, Rainer On 08.07.2011 05:41, Konstantin Kolinko wrote: > Running 7.0.18 behind Apache HTTPD, > using Ajp connector (Bio), > > for every actual request there are two records in the access log, > one "true" record, followed by a blank one. > > E.g.: > ipaddress - username [08/Jul/11:07:16:05 +0400] "GET /manager/html > HTTP/1.1" 200 24854 > ipaddress - - [08/июл/11:07:16:05 +0400] "-" 400 - > ipaddress - username [08/Jul/11:07:16:05 +0400] "GET > /manager/images/asf-logo.gif HTTP/1.1" 304 - > ipaddress - - [08/июл/11:07:16:05 +0400] "-" 400 - > ipaddress - username [08/Jul/11:07:16:06 +0400] "GET > /manager/images/tomcat.gif HTTP/1.1" 304 - > ipaddress - - [08/июл/11:07:16:06 +0400] "-" 400 - > > These extra log entries are absent in Apache HTTPD logs. > > > This issue is specific to AJP. When I tested with HTTP x Bio/Nio/Apr > the logs were operating correctly. > > It is not pretty, but it does not look like a show stopper. > > > This issue is observed with 7.0.17 as well. I have not tested 7.0.16 > in this configuration. > > Best regards, > Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
