Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 33187 invoked from network); 20 Jan 2006 10:05:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Jan 2006 10:05:03 -0000 Received: (qmail 74600 invoked by uid 500); 20 Jan 2006 10:04:47 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 74518 invoked by uid 500); 20 Jan 2006 10:04:46 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 74496 invoked by uid 99); 20 Jan 2006 10:04:46 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2006 02:04:46 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of foojava@googlemail.com designates 66.249.92.206 as permitted sender) Received: from [66.249.92.206] (HELO uproxy.gmail.com) (66.249.92.206) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jan 2006 02:04:45 -0800 Received: by uproxy.gmail.com with SMTP id o2so249309uge for ; Fri, 20 Jan 2006 02:04:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=X6u0LjZSDbd4HEA03HXEV4MWvJLa30GFTF8vK/9y7d1z8MM2CyifwQGYcRORANYj2A1LAYq7IxYyt22cYqylNteyf4ZsLoIY99lv4PdG6Zmw7gK8ZVnZFCtr7s7RTYZ6wv4BEzDgD76ZJPuJ2xRCig8CwCLiVfLB5pAblWyp69k= Received: by 10.66.219.19 with SMTP id r19mr702931ugg; Fri, 20 Jan 2006 02:04:23 -0800 (PST) Received: by 10.66.241.7 with HTTP; Fri, 20 Jan 2006 02:04:22 -0800 (PST) Message-ID: <5669b15b0601200204w85e08edq3169111b5e2254b6@mail.gmail.com> Date: Fri, 20 Jan 2006 11:04:22 +0100 From: foo java To: Jakarta Commons Users List Subject: Re: coomons dbcp refresh connections - how? Cc: praveen.gunda@gmail.com In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5271_24049497.1137751462525" References: <5669b15b0601180756k4c964d81s28f44bdf5e8d4039@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_5271_24049497.1137751462525 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Thanks for your reply. Do you mean to say it is a default feature of dbcp? = I don't think so. Or have you put some configuration setting to get the connections refreshed= . Please reply. Regards, foojava On 1/18/06, praveen gunda wrote: > > Once DBCP notices a stale connection it refreshes that connection. > I have been using this from a year now. Our DB is restarted every sunday > morning and I rarely have problems with the connections. > > DBCP seems to refresh the connections for me. But anyway my pool size is > fairly low, so my connection pool is refreshed in no time. > > > > On 1/18/06, foo java wrote: > > > > Hi, > > > > I am using jakarta commons DBCP package to pool the jdbc connections. I > am > > wondering is there any way with it to refresh the connections between > pool > > and database? > > > > Say, in case at the start the connections are established between pool > and > > database. Client request and return the connection to the pool. In case > > because of network down or database down, the connection between pool > and > > db > > gets broken. Is there any way to judge and refresh the connection > between > > pool and db?? > > > > Any ideas?? > > > > regards, > > foo > > > > > > ------=_Part_5271_24049497.1137751462525--