Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 30022 invoked from network); 5 Apr 2006 15:23:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Apr 2006 15:23:43 -0000 Received: (qmail 59906 invoked by uid 500); 5 Apr 2006 15:23:14 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 59884 invoked by uid 500); 5 Apr 2006 15:23:14 -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 59873 invoked by uid 99); 5 Apr 2006 15:23:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Apr 2006 08:23:14 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of larry.meadors@gmail.com designates 66.249.82.201 as permitted sender) Received: from [66.249.82.201] (HELO xproxy.gmail.com) (66.249.82.201) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Apr 2006 08:23:13 -0700 Received: by xproxy.gmail.com with SMTP id t16so1224362wxc for ; Wed, 05 Apr 2006 08:22:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pJsHbjqcRLjvsSaRqUEgXoJBHhW04hJI8E87D8HfjRthgd4jBb8jGQtVz8LZv8kPOcT99tzyrVOo8ui6nYEGJ+RYGYQatLuMW87YKCjZ4J8SuQAMGdy8wKz6xnCepJXtzNTJPJvQsy64vvykAilG9ch5B/oHoQ7S9VD7Fo9op4w= Received: by 10.70.69.6 with SMTP id r6mr5207858wxa; Wed, 05 Apr 2006 08:22:52 -0700 (PDT) Received: by 10.70.74.19 with HTTP; Wed, 5 Apr 2006 08:22:52 -0700 (PDT) Message-ID: Date: Wed, 5 Apr 2006 09:22:52 -0600 From: "Larry Meadors" Reply-To: lmeadors@apache.org Sender: larry.meadors@gmail.com To: "Tomcat Users List" Subject: Re: need inputs on connection pool In-Reply-To: <20060405151511.54203.qmail@web8614.mail.in.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4433DCA6.6050305@verizon.net> <20060405151511.54203.qmail@web8614.mail.in.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Calling close() on a pooled connection simply returns it to the pool, however, i have seen some cases where calling ti twice closes it for real. Don't do that. If you are interested in other options that eliminate that concern, you may want to try iBATIS - you would still use SQL, but it manages the connections, statements, resultsets, etc, and maps the results of the SQL to objects. Larry On 4/5/06, Abh N wrote: > Hi, > > we are implementing the connection pooling in our application. > > connections are taken from the data source. > > After getting the connection i need to confirm whether i have to explic= tly close the connection > like conn.close () > > i want to know in above case whether connection will be release to the = pool or will get closed. > > i have a doubt as in above case the connection might be getting closed = and might not be available for re-use. > > > > > --------------------------------- > Jiyo cricket on Yahoo! India cricket > Yahoo! Messenger Mobile Stay in touch with your buddies all the time. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org