On Wed, 21 Mar 2001 [EMAIL PROTECTED] wrote:
| What about 33 sec. ? It matches the version :-)
|
| ( seriously - does the HTTP spec have any number ? If not, can we use
| whatever apache is using ? )
|
| In any case - 300s is better than no timeout - and if it's too much we can
| reduce it later ( and make it configurable anyway ).
Isn't there an issue with tomcat closing a connection before apache does?
At least it seems so to me. If you restart tomcat while the browser is
connected to it through apache-mod_jk, then that apache process will use
all available CPU right away.
I guess this is a bug of some sort, just wanted to mention it, especially
now since it seems like you'd want tomcat to close connections before
apache does.. Or whatever you're up to! ;)
--
Mvh,
Endre
