> -----Original Message----- > From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] > Sent: Monday, May 18, 2009 4:02 PM > To: Tomcat Users List > Subject: RE: Running out of tomcat threads - why many threads in > RUNNABLEstage even with no activity > > > From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] > > Subject: RE: Running out of tomcat threads - why many threads in > > RUNNABLEstage even with no activity > > > > From whatever I have read on this, it seems to me that this could > > happen if a servlet writes something to a response stream, closes > > the response stream, but after that keeps on doing some processing > > (e.g. running an infinite loop). > > No - the thread would be inside the servlet in that case. The thread here > in the RUNNABLE state is waiting for a *new* request to come in over an > active AJP connection; a thread in the WAITING state would be assigned to > a new connection when one is accepted. >
[Pantvaidya, Vishwajit] Ok - so then the question is when does tomcat transition the thread from Running to Waiting? Does that happen after AJP drops that connection? So could the problem be occurring here because AJP is holding on to connections? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
