commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DBCP-375) initialSize < minIdle => non-performing query plans are chosen
Date Thu, 30 Jan 2014 22:02:09 GMT

     [ 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)

Mime
View raw message