From dev-return-73641-apmail-tomcat-dev-archive=tomcat.apache.org@tomcat.apache.org Fri Aug 04 18:18:34 2006 Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 86274 invoked from network); 4 Aug 2006 18:18:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Aug 2006 18:18:33 -0000 Received: (qmail 10554 invoked by uid 500); 4 Aug 2006 18:18:30 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 9948 invoked by uid 500); 4 Aug 2006 18:18:29 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 9936 invoked by uid 99); 4 Aug 2006 18:18:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Aug 2006 11:18:29 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jamey@elementalsecurity.com designates 67.102.209.26 as permitted sender) Received: from [67.102.209.26] (HELO vscan2.elementalsecurity.com) (67.102.209.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Aug 2006 11:18:25 -0700 Received: from curie.esi.elementalsecurity.com (a-67-102-209-17.elementalsecurity.com [67.102.209.17]) by vscan2.elementalsecurity.com (Postfix) with ESMTP id 7ECA4B019 for ; Fri, 4 Aug 2006 18:18:05 +0000 (GMT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Out of Threads error Date: Fri, 4 Aug 2006 11:18:04 -0700 Message-ID: <2AEB99194E9D654CA67FF3039E8ACFBC01155ED3@curie.esi.elementalsecurity.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Out of Threads error Thread-Index: Aca38lPXW3N2V+CiQWO61fulYtbKUw== From: "James Courtney" To: "Tomcat Developers List" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I'm getting this message from my Tomcat 5.0.28 on Linux. 2006-08-02 21:01:19: ERROR All threads (400) are currently busy, waiting. Increase maxThreads (400) or check the servlet status Originally I had 200 threads configured and now 400 in an attempt to avoid it. Either number seems larger than what should be necessary. It seems quite likely that there's an application issue causing all threads to block and accumulate or something so I need to do a kill -3 next time it happens to try and see what everyone is up to. That said, I was attempting to grep the Tomcat source code for where this message is logged and thus where I hoped to find and understand better the thread manager. I grepped for "Increase maxThreads", "Increase", and "are currently busy" all to no avail in finding the code doing the logging. Is the code which logs this message part of a dependency library not in the tomcat source tree? If so, which one please. I just want to understand the application behavior when the limit is reached. Many thanks! Jamey --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org