[
https://issues.apache.org/jira/browse/DBCP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved DBCP-210.
------------------------------
Resolution: Fixed
The duplicate is looking at a slightly different issue but the solution is the
same - use a custom eviction policy which it is now possible to configure with
DBCP2.
> 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)
