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 2D61810F21 for ; Thu, 30 Jan 2014 22:02:34 +0000 (UTC) Received: (qmail 60212 invoked by uid 500); 30 Jan 2014 22:02:11 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 60061 invoked by uid 500); 30 Jan 2014 22:02:10 -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 60041 invoked by uid 99); 30 Jan 2014 22:02:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Jan 2014 22:02:09 +0000 Date: Thu, 30 Jan 2014 22:02:09 +0000 (UTC) From: "Mark Thomas (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (DBCP-375) initialSize < minIdle => non-performing query plans are chosen 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-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Thomas resolved DBCP-375. ------------------------------ Resolution: Won't Fix I don't really see what the DBCP developers can do about this. I suspect it is a feature of the JDBC driver. Feel free to re-open this if there is a DBCP issue to be fixed. We'll need a test case that demonstrates it - ideally in the form of a unit test. > initialSize < minIdle => non-performing query plans are chosen > -------------------------------------------------------------- > > Key: DBCP-375 > URL: https://issues.apache.org/jira/browse/DBCP-375 > Project: Commons Dbcp > Issue Type: Bug > Affects Versions: 1.2.1, 1.2.2, 1.3, 1.4 > Environment: * dhcp 1.2.1, pool 1.2 (issue also tested with latests library version => still there) > * java 6 > * oracle 10.2 and 11 (ojdbc 4 - 6) > * hibernate 2.1.8 > Reporter: Patrick Hammer > > We found a strange behaviour when setting initialSize=0 and minIdle=10: > * non-performing query plans are used on the DB > * correct query plans are used by "small" java app without dhcp and pool (or by sqldeveloper) > Analysis: > * DB tracing showed no difference between the inputs of performing/non-performing queries > * ojdbc tracing showed no difference neither > Work-around: > * set initialSize = minIdle, e.g., both to 10. -- This message was sent by Atlassian JIRA (v6.1.5#6160)