Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 83647 invoked from network); 4 Nov 2003 21:44:04 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Nov 2003 21:44:04 -0000 Received: (qmail 25343 invoked by uid 500); 4 Nov 2003 21:43:33 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 24984 invoked by uid 500); 4 Nov 2003 21:43:30 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: 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 24971 invoked from network); 4 Nov 2003 21:43:30 -0000 Received: from unknown (HELO frenzy) (216.138.231.61) by daedalus.apache.org with SMTP; 4 Nov 2003 21:43:30 -0000 Received: from h61.c231.tor.velocet.net ([216.138.231.61] helo=spectacle.ca) by frenzy with esmtp (Exim 3.35 #1 (Debian)) id 1AH98t-0007VS-00 for ; Tue, 04 Nov 2003 16:55:15 -0500 Message-ID: <3FA81DF7.6030005@spectacle.ca> Date: Tue, 04 Nov 2003 16:45:27 -0500 From: Erik Wright User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Severe notification ... References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, I have had this problem exactly, and have been told that it is a bug in 4.1.24 to 4.1.27 that has been fixed in 4.1.29. Essentially, when working at or near the maximum connections (as defined in the Connector config in server.xml) some threads get permanently deadlocked or something. I didn't investigate much more than that. I created my own workaround which is really a hack not worth sharing here. Perhaps when I have time I will upgrade to 4.1.29 and see if that fixes the problem. If you do upgrade, please post your results to the list! Erik Mufaddal Khumri wrote: > I have my webapp up and running and am stress testing it. After a > while I get this: > > "Nov 4, 2003 1:50:12 PM org.apache.tomcat.util.threads.ThreadPool logFull > SEVERE: All threads are busy, waiting. Please increase maxThreads or > check the servlet status75 75" > > I have no idea why all threads would be busy and waiting. > > I could raise the value of maxThreads, but that would just delay the > error from being reported. I need to get a dump of my tomcat threads > and see where the bottleneck is. How do I do this ? Is there a > facility in tomcat that would allow me to dump its threads and allow > me to see where the threads are waiting and not moving on ? Is there a > good utility i can use ? > > Thanks. -- http://www.spectacle.ca/ The New Online Source for Live Music in Montreal .::514.286.1699::. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org