Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 89656 invoked from network); 10 Sep 2005 22:57:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Sep 2005 22:57:36 -0000 Received: (qmail 80779 invoked by uid 500); 10 Sep 2005 22:57:21 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 80765 invoked by uid 500); 10 Sep 2005 22:57:21 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 80752 invoked by uid 99); 10 Sep 2005 22:57:21 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Sep 2005 15:57:21 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: 212.216.176.118 is neither permitted nor denied by domain of malcolm@villeinitalia.com) Received: from [212.216.176.118] (HELO vsmtp14.tin.it) (212.216.176.118) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Sep 2005 15:57:32 -0700 Received: from [127.0.0.1] (212.171.48.180) by vsmtp14.tin.it (7.2.060.1) id 42FDFA9300865556 for tomcat-user@jakarta.apache.org; Sun, 11 Sep 2005 00:57:16 +0200 Message-ID: <432364BE.4050302@villeinitalia.com> Date: Sun, 11 Sep 2005 00:57:02 +0200 From: Malcolm Warren User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: tomcat-user@jakarta.apache.org Subject: AJP connector maxthreads problem Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I've got Tomcat 4.1.30 and Apache 1.3 on Linux and I've been using the jk2 connector for a year and a half without any problems. Now I've suddenly got Tomcat stopping with the following message: All threads (75) are currently busy, waiting. Increase maxThreads (75) or check the servlet status. Now I've done a lot of homework, googled and searched the jakarta site, but I can't seem to get answers to my specific questions, which if any of you are willing to help me, should be fairly simple to answer. 1) We have only a moderately busy site with about 500 new visitors entering from outside every day, so it would have thought it would be fairly difficult for them to use up all the 75 connections at the same time, but I do have some programmes that create their own threads, though in a fairly limited way. In your expert view are 75 jk2 connections sufficient for this kind of moderate use, or is it likely I've some kind of problem I've got to get to the bottom of? I've been through my recent new applications, and there really is nothing that could have created this problem recently. 2) I've set connectionTimeout=20000, which seems to be what everybody else was setting it to, can I reduce this without any problem? It seems quite long, 20 seconds, why hang on to connections for so long, or is there a lot of overhead in creating them? 3) If I want to, can I increase my max connections to 125 without any qualms? - This would appear to be the simplest solution here. Thanks for any help on this. Regards, Malcolm Warren --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org