ar...@bca-group.com wrote:
So I assume adding connectionTimeout attribute to the connector config
could help mitigate this?
The connectionTimeout of the Tomcat AJP <Connector> says this :
connectionTimeout
The number of milliseconds this Connector will wait, after accepting a connection, for the
request URI line to be presented. The default value is infinite (i.e. no timeout).
So that applies to something totally different. It is more of a measure to avoid DoS
attacks whereby a client would connect to this Connector, and then not send any request
over that connection for an extended period of time.
This would lock up the connector (waiting for the request), and if there were enough such
requests at the same time, could lock up the entire server.
To get back to your issue : in this case, the warning is normal and justified. Tomcat is
supposed to send a complete response, but for some reason it cannot. And it cannot do
anything else useful with this unsent response part. So it is letting you know, instead
of just keeping mum about it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
