Rainer, Thank you for your reply.
My main question here is: is it normal that that a faulty application takes down the whole site? I have seen applications with this problem several times, and all the 40ish Tomcats we have are configured with connectionTimeout set to zero - and connection_pool_timeout as well on the JK side - but this never hung the whole site so far (and I am talking about eight or nine years, if not more). Rainer Jung-3 wrote: > >> JK 1.2.26 (/maybe some other 1.2.2x version but cannot be sure) > > You and we need to be sure. Set you JK log level to at least info. All > Apologies, I was definitely not clear. The thing is happening with JK version 1.2.26, and I remember having a problem with some 1.2.2x version - but I cannot tell for sure now if it was the same problem because I rapidly upgraded. > Tomcat 5.5.9 / 5.5.27 > JDK 1.5.0_12 / 1.5.0_16 / 1.6.0_07 And here, that I experienced the same with the above versions and with the same application. It is currently running with 5.5.27 on 1.6.0_07. Rainer Jung-3 wrote: > > 1) Finding the real reason: Assuming some requests send to your Tomcat > simply get stuck and do not return fast enough, you'll need to take > thread dumps of Tomcat and look at those. Take the dumps when the > problem is there and take more than one, e.g. 3 dumps each 3 seconds > apart from the previous one. > Thanks. I will give this a try, though my main priority is to have the site working, not the single application. I suspect there are some problem releasing the db connections, but I am not the developer nor a modern-Java-with-tons-of-frameworks developer. :-) Rainer Jung-3 wrote: > > 2) Making IIS/mod_jk more robust against the problem: Use timeouts as > described on page > > http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html > > Those will not make your app work, when in fact requests in Tomcat get > stuck and block all available connector threads, but it will at least > keep iis/mod_jk running. > Actually, I was about to try this when I found that restarting Tomcat cured the problem. I will try with the suggested timeouts as soon as everyone stops watching. As I was writing above, I am stumped to see a single app stopping the web server, because we have a zero timeout on all Tomcats and apps since years, and no problems like this. I myself thought this was just not possible, so it took long time to figure this out. BTW, thanks for writing the timeouts page, it was really needed. :-) Br1. -- View this message in context: http://www.nabble.com/JK-and-IIS---troubles--tp19750760p19768252.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]
