tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 60511] org.apache.coyote.ajp.AjpNio2Protocol sends wrong data to Apache MOD_JK connector causing connection closure and multiple reconnects
Date Thu, 22 Dec 2016 22:54:57 GMT
https://bz.apache.org/bugzilla/show_bug.cgi?id=60511

--- Comment #3 from Rainer Jung <rainer.jung@kippdata.de> ---
Just in case this is not clear: it seems sometimes the request is immediately
answered with an AJP packet with signature "05", which is an "End Response"
packet. No response headers, just "End Response".

Of course it could be, that the request was invalid and the connector
immediately closed the connection.

Looking at the AJP connector code, the endAndCloseMessageArray was sent in
finish() and getErrorState().isError() was true.

I'd agree, that it would be helpful to reproduce the problem with a current
version and to try to provide a self-contained reproduction example. From your
full log it seems that sometimes correct responses come back, so we need to
understand what properties the failing requests distinguish from the good ones.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message