Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 76290 invoked from network); 26 Dec 2006 15:29:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Dec 2006 15:29:03 -0000 Received: (qmail 15978 invoked by uid 500); 26 Dec 2006 15:29:03 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 15911 invoked by uid 500); 26 Dec 2006 15:29:03 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 15900 invoked by uid 500); 26 Dec 2006 15:29:03 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 15897 invoked by uid 99); 26 Dec 2006 15:29:03 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Dec 2006 07:29:03 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Dec 2006 07:28:55 -0800 Received: by brutus.apache.org (Postfix, from userid 33) id 2CF907142BF; Tue, 26 Dec 2006 07:28:35 -0800 (PST) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 40000] - tomcat / context freezes when hitting maxActive parameter in (oracle) database resource In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20061226152835.2CF907142BF@brutus.apache.org> Date: Tue, 26 Dec 2006 07:28:35 -0800 (PST) X-Virus-Checked: Checked by ClamAV on apache.org 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://issues.apache.org/bugzilla/show_bug.cgi?id=40000 yoavs@computer.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From yoavs@computer.org 2006-12-26 07:28 ------- Don't set maxWait to -1. If you set it to something reasonable, when the pool is fully busy (i.e. active = maxActive), the pool will wait forever if maxWait = -1, hence the behavior you're seeing. If I set maxWait to a positive value I get the exception back right away as expected. Either way, if there's a bug here, it's much more likely a DBCP bug. It's DBCP doing the waiting. If you have a stack trace showing hung threads in Tomcat function calls after the queries have completed (not before), please feel free to reopen this issue and attach said stack trace. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org