Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 90417 invoked from network); 9 Jul 2004 00:26:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Jul 2004 00:26:27 -0000 Received: (qmail 74349 invoked by uid 500); 9 Jul 2004 00:26:06 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 74075 invoked by uid 500); 9 Jul 2004 00:26:04 -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 74050 invoked by uid 99); 9 Jul 2004 00:26:04 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [202.164.169.219] (HELO mail.eastwestbanker.com) (202.164.169.219) by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 08 Jul 2004 17:26:01 -0700 Received: (qmail 25345 invoked by uid 508); 9 Jul 2004 00:56:24 -0000 Received: from unknown (HELO ?172.30.19.57?) (172.30.19.57) by 0 with SMTP; 9 Jul 2004 00:56:23 -0000 Message-ID: <40EDE614.8080909@mylife.ph> Date: Fri, 09 Jul 2004 08:25:56 +0800 From: Eric Noel User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en, en-us, ko, ko-kr MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Limit time for Database connection References: <40EDE29A.9080304@berkeley.edu> In-Reply-To: <40EDE29A.9080304@berkeley.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On 7/9/2004 8:11 AM, Robert F. Hall wrote: > Elisabeth, > > Nobody has responded to your question (that I've seen), so I'll "take a > shot". > > This sounds like a network issue, and network connection failures have > to "time out" > before they fail. Using a timed separate thread to obtain the > connections for the pool > occurs to me; if the connection thread doesn't return in a certain > amount of time the > parent thread could throw an Exception. > > Has anybody tired something along these lines? Is this suggestion way > off base? > > Regards, > Robert > > > Bachler, Elisabeth (Elisabeth) wrote: > >> Hello, >> I defined a database connection that uses a pool connection. >> Everything is >> working well. >> Now I had a routing problem that prevented any database connection >> (with a >> SQPNestedException fired). The exception fired after a long time.... is >> there a way of setting the connection limit, so it does not take so long >> before firing the exception? >> >> Thanks >> Elisabeth >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org >> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org >> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > I thought it would be just as simple as setting the parameter in the DBCP??? maxWait 10000 --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org