[
https://issues.apache.org/jira/browse/DBCP-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151657#comment-17151657
]
Robert Paschek commented on DBCP-566:
-------------------------------------
Please have a look at this PR: https://github.com/apache/commons-dbcp/pull/42
> Clear PreparedStatement pool when connection is returned to the pool
> --------------------------------------------------------------------
>
> Key: DBCP-566
> URL: https://issues.apache.org/jira/browse/DBCP-566
> Project: Commons DBCP
> Issue Type: New Feature
> Reporter: Robert Paschek
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With the current configuration option poolPreparedStatements true the
> statements are held open for the lifetime of the connection. This results in
> cursors being open and locks in the database for a long time, which could
> cause problems with administrative tasks in the database.
> There should be an additional configuration clearStatementPoolOnReturn. When
> set to true, the pool will be cleared and the statements closed when the
> connection is returned to the pool. Default can be false to retain the
> current behaviour.
> With this the application can still benefit from the Statement-cache in mass
> operations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
