Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 97538 invoked by uid 500); 5 Sep 2001 19:56:35 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: tomcat-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 97525 invoked from network); 5 Sep 2001 19:56:35 -0000 Message-ID: <024201c13644$d4e46b20$9c0c0a0a@sega.corp> From: "...amy.nanninga..." To: References: <1130593DB152D41186F300508B9B136E02A44117@mail2.imedlink.net> <4.3.2.7.2.20010904161330.02c4d948@mail.xythos.com> Subject: ThreadPool: Pool exhausted with 100 threads Date: Wed, 5 Sep 2001 12:56:19 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hello, We are seeing many many 'ThreadPool: Pool exhausted with 100 threads' errors. Ive seen that you can modify the server.xml to customize threadpool access (max_threads value=x max_spare_threads vaule=x, min_spare_threads value=x), but Ive also heard that its hard coded in org.apache.tomcat.util.ThreadPool.java in Tomcat 3.2.2. This is our production env so Id hate to impliment this and have the prolem become bigger. What do you guys suggest? We are using Tomcat 3.2.2, Apache 1.3 (with ssl mod) as our webservers, on Solaris 7, with Oracle 8 via jdbc. Mucho Thanks........ ::'::........amy... ................end.transmission.......::':: \\*//