You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2014/02/05 23:38:09 UTC

[jira] [Commented] (DBCP-210) Have dbcp close pooled prepared statements after some settable time limit

    [ https://issues.apache.org/jira/browse/DBCP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892681#comment-13892681 ] 

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łaczkowski
>             Fix For: 2.0
>
>
> The problem is, when poolPreparedStatements is set to true and the database is heavy loaded, the prepared statements are never closed. After some time, as the database contents changes, they become unoptimal. It would be nice to have another parameter telling for how long each statement can be kept open. 



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