tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br1 <>
Subject Re: JK and IIS - troubles?
Date Wed, 01 Oct 2008 22:04:29 GMT


Good evening.

Rainer Jung-3 wrote:
>> My main question here is: is it normal that that a faulty application
>> takes
>> down the whole site?
> Yes, unfortunately that's a common source for trouble. If an app doesn't
> finish processinf a request, e.g. because it wais without timeout for
> some other service, or runs in a loop, or has a deadlock, then each
> broken request will block a thread until finally - maybe after weeks -
> all threads are blocked in the buggy requests of the single app.
Again, not so common for me, nor - sorry - for what I found on the whole
list so far.
So, one should not think that setting a worker's connection_pool_size to x
would limit the web server to use no more than x threads for that worker? 
This was happening with peaks of every two hours or so, but I guess it
depends on the site traffic.

Rainer Jung-3 wrote:
> The Thread Dumps are an exciting way of bridging the gap between the
> operations people and the developers. Operations people can provide it,
> and developers can read it. Actually it is not that hard to read for
> operations people too.
Thanks. I will let you know how the specific developer and operation person
will react (though I doubt we will ever give a Thread Dump party), but again
this is not the main priority at the moment. Also, I would not be happy to
let the site hang again to take a thread dump - though I could fix the
timeouts first maybe as you say below, and avoid another downtime. 

Rainer Jung-3 wrote:
> Beware, that the timeouts will shield IIS, but if the Tomcat can't
> handle more requests, the timeouts in the IIS plugin will not heal Tomcat.
Thank you for telling me. It sounds fair some way..  and it's definitely
what is needed to take a thread dump without killing everything..  

Rainer Jung-3 wrote:
>> BTW, thanks for writing the timeouts page, it was really needed. :-)
> Yes it was, sorry that it took that long.
It's okay, just a wrong timeout.. it happens to the most of us here. :-)

View this message in context:
Sent from the Tomcat - User mailing list archive at

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message