You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Piotr Kołaczkowski (JIRA)" <ji...@apache.org> on 2007/02/05 13:14:06 UTC
[jira] Created: (DBCP-210) Have dbcp close pooled prepared
statements after some settable time limit
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
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (DBCP-210) Have dbcp close pooled prepared
statements after some settable time limit
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ 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: 1.3
This is sort of a consequence of pooling prepared statements, so an argument could be made for "Wont Fix", but ideas / patches for how to satisfy this request without impacting pool performance will be considered in 1.3.
> 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: 1.3
>
>
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[jira] Updated: (DBCP-210) Have dbcp close pooled prepared
statements after some settable time limit
Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.
[ 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.3)
1.4
Moving to 1.4 where more robust pool and pooled object lifecycle features will be considered.
> 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: 1.4
>
>
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org