> Insofar as any of us can predict the future, I would say the answer to
this is
> definitely yes. Among other things, the lack of a timeout creates a
pretty easy
> DOS attack against a Tomcat server -- simply open enough socket
connections to
> exhaust the configured pool size, and just sit ther
John Neffenger wrote:
> I was pleased to see that a connection timeout has been added to Tomcat
> 4.0 in the HttpConnector class. A timeout was missing in Sun's JSDK
> through version 2.0 and in earlier versions of Tomcat. Without a
> timeout, the servlet runner process accumulates dead connect
I was pleased to see that a connection timeout has been added to Tomcat
4.0 in the HttpConnector class. A timeout was missing in Sun's JSDK
through version 2.0 and in earlier versions of Tomcat. Without a
timeout, the servlet runner process accumulates dead connections on the
Internet and, with
