Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 45443 invoked from network); 5 Oct 2010 13:28:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Oct 2010 13:28:06 -0000 Received: (qmail 27825 invoked by uid 500); 5 Oct 2010 13:28:03 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 26572 invoked by uid 500); 5 Oct 2010 13:27:59 -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 26563 invoked by uid 99); 5 Oct 2010 13:27:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Oct 2010 13:27:59 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=FORGED_HOTMAIL_RCVD2,FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Oct 2010 13:27:52 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1P37YK-0002Kq-0S for users@tomcat.apache.org; Tue, 05 Oct 2010 06:27:32 -0700 Message-ID: <29887279.post@talk.nabble.com> Date: Tue, 5 Oct 2010 06:27:32 -0700 (PDT) From: mamalacation To: users@tomcat.apache.org Subject: RE: tomcat 6.0 bottleneck In-Reply-To: <99C8B2929B39C24493377AC7A121E21F99EBF4F570@USEA-EXCH8.na.uis.unisys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mamalacation@hotmail.com References: <29885725.post@talk.nabble.com> <99C8B2929B39C24493377AC7A121E21F99EBF4F570@USEA-EXCH8.na.uis.unisys.com> X-Virus-Checked: Checked by ClamAV on apache.org n828cl, n828cl wrote: > > > Pretty much guaranteed that it's not Tomcat but your webapp that is > locking itself out of access to some resource (such as the database). > Take several thread dumps during the slowdown period and see what's going > on. > > http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F > http://wiki.apache.org/tomcat/FAQ/Performance_and_Monitoring > > BTW, tell us the *exact* Tomcat version, and the JVM level you're running > on. > > as far as the version as concerned: Tomcat Version: 6.0.26 JVM Version : 1.6.0_20-b02 JVM Vendor : Sun Microsystems Inc. I will look at the links you proposed to see what's going on with my webapps, but I am pretty sure that there must be some limit somewhere that I can't see. Where can I set the database options regarding timouts, pool size, max_database_connections, etc? thanx again, mamalos -- View this message in context: http://old.nabble.com/tomcat-6.0-bottleneck-tp29885725p29887279.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org