Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 66773 invoked from network); 9 May 2003 20:35:41 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 May 2003 20:35:41 -0000 Received: (qmail 17211 invoked by uid 97); 9 May 2003 20:37:50 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 17204 invoked from network); 9 May 2003 20:37:49 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 9 May 2003 20:37:49 -0000 Received: (qmail 65832 invoked by uid 500); 9 May 2003 20:35:31 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 65821 invoked from network); 9 May 2003 20:35:31 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 May 2003 20:35:31 -0000 Received: (qmail 17197 invoked by uid 50); 9 May 2003 20:37:40 -0000 Date: 9 May 2003 20:37:40 -0000 Message-ID: <20030509203740.17196.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 19799] - Tomcat dies after being up for a while (complains about maxThreads) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19799 Tomcat dies after being up for a while (complains about maxThreads) ------- Additional Comments From akelley@ecsplus.com 2003-05-09 20:37 ------- I will spend some time thinking about it and see where I can get. Just so you know, this problem has appeared at two different client sites with the same application (both running Linux). The problem appeared after changing the database pool we are using (may or may not be related). I have experienced this problem with the following versions of Tomcat: 4.1.12 4.1.18 4.1.24 More info to come hopefully. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org