Hi Rainer,
Rainer Jung-3 wrote: > > Yes it does limit it that way. But when a timeout fires in mod_jk, > Tomcat is not aware of it and will still proceed working on the request. > Your web server though receives new rquests and forwards them, so Tomcat > could run out of memory. > If there was a way to set the maximum request processing time on Tomcat.. you can do it in ASP.. :-) Rainer Jung-3 wrote: > > Are you saying, that you can't get any content from IIS, even not > content, that does not involve Tomcat to be returned? > Exactly, the whole site hangs. Everything stops working, with no exceptions. Local static and dynamic content, all remote Tomcat workers, other remote stuff in php we have, everything. No error in the event log, the IIS processes just stay there idle. Rainer Jung-3 wrote: > > If so, what is your connection pool size? The default is 250, which is > quite high. > I did not go too far, it was the default, after some time I set it to 300 but this did not change anything. Rainer Jung-3 wrote: > > Thread Dumps only halt the JVM for a couple of milliseconds. No need to > be afraid of them, even in serious production. Don't mix the notions of > thread dump and memory dump though. The latter takes quite long, but is > not what you need here. > Yes, but I am just afraid of my site hanging as I was explaining above. :-) Thank you, br1. -- View this message in context: http://www.nabble.com/JK-and-IIS---troubles--tp19750760p19775890.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
