Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 6684 invoked from network); 19 Jun 2007 14:53:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jun 2007 14:53:35 -0000 Received: (qmail 91441 invoked by uid 500); 19 Jun 2007 14:53:27 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 91423 invoked by uid 500); 19 Jun 2007 14:53:27 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 91400 invoked by uid 99); 19 Jun 2007 14:53:27 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jun 2007 07:53:27 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [88.198.191.179] (HELO zoe.2sheds.de) (88.198.191.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jun 2007 07:53:22 -0700 Received: from [10.51.2.99] (h-213.61.105.92.host.de.colt.net [213.61.105.92]) by zoe.2sheds.de (Postfix) with ESMTP id BF60F55429 for ; Tue, 19 Jun 2007 16:53:00 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <64155737-54A2-4707-A7E7-3CE392E0B8EE@2sheds.de> Content-Transfer-Encoding: 7bit From: Andrew Miehs Subject: Re: How can i configure tomcat to avoid threads error in tomcat Date: Tue, 19 Jun 2007 16:53:02 +0200 To: "Tomcat Users List" X-Pgp-Agent: GPGMail 1.1.1 (Tiger) X-Mailer: Apple Mail (2.752.2) X-Virus-Checked: Checked by ClamAV on apache.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/06/2007, at 4:45 PM, Prashant Thakkar wrote: > Hi, > > Thanks, > But this is the clients application which we are running. We dont > have the > access to the servlet code. That was the the obvious reason we had > increased > the thread limit to 250. Is the server running a lot of traffic? Then you may want to increase this even further. Is the CPU load of the server at 100%? If so, the clients software probably has an infinite loop - and no amount of config 'tuning' will fix this. > Other thing i would like to know is about the thread pooling. How > can i use > this with tomcat 5.0.28 What do you mean exactly by thread pooling? Andrew -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFGd+3OW126qUNSzvURAnt7AJ9ciXedLgRkgMSiEELTcfalAaPFOwCfR81w /N4rNbJfMiZ1FKJLIGILbxI= =6+1V -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org