Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 53779 invoked from network); 26 May 2003 21:22:03 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 26 May 2003 21:22:03 -0000 Received: (qmail 16884 invoked by uid 97); 26 May 2003 21:24:18 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 16877 invoked from network); 26 May 2003 21:24:17 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 26 May 2003 21:24:17 -0000 Received: (qmail 52382 invoked by uid 500); 26 May 2003 21:21:51 -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 52371 invoked from network); 26 May 2003 21:21:50 -0000 Received: from moutng.kundenserver.de (212.227.126.171) by daedalus.apache.org with SMTP; 26 May 2003 21:21:50 -0000 Received: from [212.227.126.155] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19KPPo-0001Su-00 for tomcat-user@jakarta.apache.org; Mon, 26 May 2003 23:21:56 +0200 Received: from [217.225.132.121] (helo=aragorn) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 19KPPn-0000EE-00 for tomcat-user@jakarta.apache.org; Mon, 26 May 2003 23:21:56 +0200 From: "Jan Behrens" To: "Tomcat Users List" Subject: RE: DB Connection Date: Mon, 26 May 2003 23:19:18 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20030526211336.7011.qmail@web20504.mail.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks to you both, sorry about my misleading post. I understand that, in using a connection pool i can get Tomcat to handle the number of connections at any given time. Is that correct? If I still have to ensure that all ResultSet's and connections have to be closed, then where is the advantage? And, would it be a good idea to automatically close abandoned connections after a certain amount of time? Regards Jan > -----Original Message----- > From: Dave Mock [mailto:dave_mock2003@yahoo.com] > Sent: Monday, May 26, 2003 11:14 PM > To: Tomcat Users List > Subject: Re: DB Connection > > > b carefull when using DBCP > always remember to close the > ResultSet/Statement/PreparedStatement and last but not > least - the Connection object > > > > > > The funny thing is this: > > > it works quite well for some time, but as soon as > > load on the app increases > > > the error appears. I therefore thought it must be > > related to the number of > > > open transactions but I am not sure. > > - edited - > > > I''d say your custom code isn't handling the DB > > connections too well, look > > into setting up a JNDI datasource and use DBCP, > > there is some documentation > > on this at: > > > > > http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-datasource-exam > ples-howto.html > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Search - Faster. Easier. Bingo. > http://search.yahoo.com > > --------------------------------------------------------------------- > 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