It depends on which <Connector> you are using. The value of "0" is simply that both the Http-Coyote and the Jk-Coyote would both behave as the docs describe for "-1".
For the Jk-Coyote Connector, you usually want the connectionTimeout disabled, or at least set to a large value (e.g. 5min). The mod_jk module will reuse the connection for different requests, so the only reason to have a connectionTimeout at all is to free up Threads after a peak-request spike. I've got a Linux 7.x box configured this way, but on my Solaris boxes I always disable 'connectionTimeout'. For Http-Coyote (aka stand-alone), you want to set this to a small number (e.g 5-15 sec.). Possibly a bit higher if you're using SSL on a light traffic site. This determines how soon a Thread is available to serve request from other clients. "Geralyn M Hollerman" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I am still looking for information about the "connectionTimeout" > attribute of a<Connector> element in server.xml, past what's in Tomcat's > Server Configuration Reference; from what I've read, the default value > is 60000 (milliseconds), but the server.xml that came with the 4.1.24 > that I downloaded is set to "0". Is there a reason for this? Does "0" do > anything special? According to the sample server.xml, "-1" disables > connection timeouts - under what situations would I want to do that? > > Thanks! > -- > Lynn Hollerman. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
