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

Posted to issues@commons.apache.org by "Phil Steitz (JIRA)" <ji...@apache.org> on 2010/02/15 05:33:31 UTC

[jira] Updated: (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:all-tabpanel ]

Phil Steitz updated DBCP-210:
-----------------------------

    Fix Version/s:     (was: 1.4)
                   2.0

> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.