Bill Barker wrote: > 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".
Yes, Coyote was what I was thinking of. > 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'. This brings up an interesting point. Is this parameter akin to Apache's "TimeOut" directive? If so, then would it not be a problem if you had the Tomcat connectionTimeout set to some low value (let's say, 1 min) and Apache TimeOut set to the default (5 min)? I would think Apache would pass a request along after, say 4 min, but Tomcat would've timed out, no? Or are they not related as I'm thinking? -- Lynn Hollerman. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
