From users-return-197252-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org Mon Jun 01 19:41:18 2009 Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 90378 invoked from network); 1 Jun 2009 19:41:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Jun 2009 19:41:18 -0000 Received: (qmail 57200 invoked by uid 500); 1 Jun 2009 19:41:26 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 57173 invoked by uid 500); 1 Jun 2009 19:41:26 -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 57162 invoked by uid 99); 1 Jun 2009 19:41:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jun 2009 19:41:26 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of arvindwill@gmail.com designates 209.85.132.240 as permitted sender) Received: from [209.85.132.240] (HELO an-out-0708.google.com) (209.85.132.240) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jun 2009 19:41:17 +0000 Received: by an-out-0708.google.com with SMTP id d11so4148371and.9 for ; Mon, 01 Jun 2009 12:40:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=U66mEuY0zmmS8JdP82K9ey/DJrlMnagf1tdN+zCgqqw=; b=QQlRkZllQ0EOKgAYpN521BxUtOz5A1+J5YIoijNBYdwT7aMamzooLrQm+r5zU9aGGm KVq+Z4n2qdXffsfp4MWPCBf6yNer0vlH3RDhfBK7gLHbMRKbUQDUQ17m3QUtAm1W27ff Lj7TeIZE0c07l1/mNDERQhp8aADzRbk1Opjag= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=l/teDB6GZclFEvrh3ixj6IoRLm4GSRQ0+mvEmNBlQJ4H/HSTO65JKV2s/ZHM/fxg8k BMN305lOnwJUnaZmSyldgPf6GbkjI126rMTRUG6+LQbFO6DaTs1eS+K6BnuJTgFub2dS gK35UvtLWlm8ccJh3fs+SO2aSOxaGm3PHGv+I= MIME-Version: 1.0 Received: by 10.101.66.15 with SMTP id t15mr5153832ank.194.1243885256194; Mon, 01 Jun 2009 12:40:56 -0700 (PDT) In-Reply-To: References: From: S Arvind Date: Tue, 2 Jun 2009 01:10:36 +0530 Message-ID: Subject: Re: Query timeout in dbcp To: Tomcat Users List Content-Type: multipart/alternative; boundary=00163662e65cd639ff046b4e9acf X-Virus-Checked: Checked by ClamAV on apache.org --00163662e65cd639ff046b4e9acf Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Is there anyother way to specify the query execution time out while establishing connection with the help of DBCP in tomcat? -Arvind S On Tue, Jun 2, 2009 at 12:56 AM, S Arvind wrote: > Is there any possibility to mention max time a query can execute from DBCP > side? our DB is Postgres and Container is tomcat 6. i dont want to give the > timeout in postgres but need to set in application side based on differnet > needs? Is it possible? > > -Arvind S > > > > "Many of lifes failure are people who did not realize how close they were > to success when they gave up." > -Thomas Edison > --00163662e65cd639ff046b4e9acf--