> From: Pantvaidya, Vishwajit [mailto:vpant...@selectica.com] > Subject: RE: Running out of tomcat threads - why many threads > inRUNNABLEstage even with no activity > > > [Pantvaidya, Vishwajit] Thanks Rainer. The RUNNABLE thread - > > is it a connection between Tomcat and webserver, or between > > Tomcat and AJP?
It's not at all clear what you mean by that. AJP is a protocol used by Tomcat and a front-end webserver, such as httpd. > > Is it still RUNNABLE and not WAITING because the servlet has > > not explicitly closed the connection yet (something like > > HttpServletResponse.getOutputStresm.close) No, the RUNNABLE is the normal state when the thread is not processing a request. The connections between Tomcat and httpd are persistent - they're never meant to close. > > [Pantvaidya, Vishwajit] My problem is that tomcat is running out of > > threads (maxthreadcount=200). Perhaps you provided some evidence earlier, but I missed it. Having threads in a RUNNABLE state waiting for requests to arrive from httpd is *normal* and expected; it's *not* a problem. You need to stop treating it like it's some terrible condition - it's how things should be. > > - Setting connectionTimeout in server.xml seems to have resolved > > the issue Only because you're throwing away what appears to be a usable connection that's designed to be persistent. > 1. Is it expected behavior that most tomcat threads are in > RUNNABLE state? As we keep telling you, yes. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
