Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CCE283D18 for ; Sat, 30 Apr 2011 17:34:42 +0000 (UTC) Received: (qmail 29389 invoked by uid 500); 30 Apr 2011 17:34:42 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 29301 invoked by uid 500); 30 Apr 2011 17:34:42 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 29290 invoked by uid 99); 30 Apr 2011 17:34:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Apr 2011 17:34:42 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Apr 2011 17:34:41 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 26E5FBBC75 for ; Sat, 30 Apr 2011 17:34:03 +0000 (UTC) Date: Sat, 30 Apr 2011 17:34:03 +0000 (UTC) From: "Phil Steitz (JIRA)" To: issues@commons.apache.org Message-ID: <1695510955.13668.1304184843156.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1341778889.8791.1303992543128.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (DBCP-357) Connection validationQuery mechanism should be replaced by new method connection#isValid() MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DBCP-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027351#comment-13027351 ] Phil Steitz commented on DBCP-357: ---------------------------------- Looks like a good enhancement for 2.0. We should probably make it configurable, though, whether to rely on the driver implementation or actually fire the validation query. > Connection validationQuery mechanism should be replaced by new method connection#isValid() > ------------------------------------------------------------------------------------------ > > Key: DBCP-357 > URL: https://issues.apache.org/jira/browse/DBCP-357 > Project: Commons Dbcp > Issue Type: Improvement > Affects Versions: 1.4, 1.4.1 > Reporter: Philippe Mouawad > Labels: PERFORMANCE > Fix For: 2.0 > > > Hello, > Current method of connection validation relies on validationQuery. > This method has a rather big performance impact on the DB (CPU, for example 3% with SELECT 1 FROM DUAL even with Oracle 10G FAST DUAL) and make an additional query for each borrow (when testOnBorrow is true). > Wouldn't it be better to use new JDBC 4 method isValid which relies on Driver check ? (Oracle would for example use its internal method ping) > Thank you > Philippe > http://www.ubik-ingenierie.com -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira