[
https://issues.apache.org/jira/browse/DBCP-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614103#comment-13614103
]
Phil Steitz commented on DBCP-372:
----------------------------------
Any other comments / suggestions on this? It might also be good to wrap and
swallow SQLException per the first patch for DBCP-264 (along with Thomas'
suggested changes).
> Statement Leak occurs when batch update is used.
> ------------------------------------------------
>
> Key: DBCP-372
> URL: https://issues.apache.org/jira/browse/DBCP-372
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.3, 1.4
> Environment: Oracle 11g
> Reporter: Naozumi Taromaru
> Priority: Critical
> Fix For: 1.4.1
>
>
> org.apache.commons.dbcp.PoolablePreparedStatement#passivate()
> execute clearBatch().
> (DBCP-264)
> But this clearBatch() throw SQLException.
> (DelegatingStatement#checkOpen() throw SQLException, because _closed is true.)
> The result,
> the PoolablePreparedStatement doesn't return to pool, and
> the PoolablePreparedStatement doesn't execute PreparedStatement#close().
> When a lot of data is processed,
> in the case of Oracle
> * ORA-00604
> * ORA-01000
> occurs.
> Proposal:
> "clearBatch();" in passivate() method
> changes as follows.
> batchAdded = false;
> getInnermostDelegate().clearBatch();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
