[
https://issues.apache.org/jira/browse/DBCP-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13969700#comment-13969700
]
Phil Steitz commented on DBCP-415:
----------------------------------
The problem, if I understand the intent of DBCP-180 and the current code
correctly, is that when statement pooling is not enabled, you do in fact need
to clean up DelegatingStatements. The one case where you do *not* want to
close-on-finalize is when the DelegatingStatement is wrapped by a PPS. So it
seems to me the safest thing to do is to find a way to guard on that condition.
> Pooled PreparedStatements may be closed when accessed
> -----------------------------------------------------
>
> Key: DBCP-415
> URL: https://issues.apache.org/jira/browse/DBCP-415
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Phil Steitz
>
> Under high concurrency, connections using pooled PreparedStatements may
> encounter SQLExceptions with messages of the form
> "org.apache.commons.dbcp2.PoolablePreparedStatement with address: 'quoted
> SQL' is closed."
--
This message was sent by Atlassian JIRA
(v6.2#6252)
