Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 5 Feb 2014 22:38:09 +0000 (UTC)
From: "Mark Thomas (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12361988.1170677577769.44691.1391639889111@arcas>
In-Reply-To: <JIRA.12361988.1170677577769@arcas>
References: <JIRA.12361988.1170677577769@arcas>
Subject: [jira] [Commented] (DBCP-210) Have dbcp close pooled prepared
 statements after some settable time limit
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DBCP-210?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D138926=
81#comment-13892681 ]=20

Mark Thomas commented on DBCP-210:
----------------------------------

With Pool 2 this should be possible via a custom eviction policy that looks=
 at how long the object has been alive.

> Have dbcp close pooled prepared statements after some settable time limit
> -------------------------------------------------------------------------
>
>                 Key: DBCP-210
>                 URL: https://issues.apache.org/jira/browse/DBCP-210
>             Project: Commons Dbcp
>          Issue Type: Improvement
>            Reporter: Piotr Ko=C5=82aczkowski
>             Fix For: 2.0
>
>
> The problem is, when poolPreparedStatements is set to true and the databa=
se is heavy loaded, the prepared statements are never closed. After some ti=
me, as the database contents changes, they become unoptimal. It would be ni=
ce to have another parameter telling for how long each statement can be kep=
t open.=20


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)