I have maxThreads set at 250. When a high percentage of that 250 are eaten up servicing essentially dead connections is when the server gets unresponsive.
What I am interested in is how tomct can know that a thread is no longer viable -say if it has been in service mode for more than 5 minutes and hasn't sent anything. --- "Bovy, Stephen J" <[EMAIL PROTECTED]> wrote: > MaxThreads > > > Stephen Bovy > Computer Associates > 6100 Center Drive > Suite 700 > Los Angeles, CA 90045 > Tel: (310) 957-3930 > Fax: (310) 957-3917 > e-mail: [EMAIL PROTECTED] > -----Original Message----- > From: August Detlefsen [mailto:[EMAIL PROTECTED] > Sent: Friday, September 02, 2005 5:21 PM > To: [email protected] > Subject: Tomcat 5.5 Running out of Threads > > Using the manager app (/manager/status) I am seeing multiple threads > in > the 'Service' mode with times of well over 60 minutes! Here is an > example: > > Stage Time B Sent B Recv Client VHost Request > S 5192947 ms 0 KB 0 KB 67.152.68.16 > dev1.mycompany.com GET / HTTP/1.1 > > I know that these connections came in during a period of particularly > heavy load and the server couldn't respond to them right away. No > response was ever sent back to the browser but the threads stay open > and > eat up a resource until the app server has to be restarted. > > Is there any setting that will cause such orphaned connections to be > terminated and returned to the pool? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
