[ https://issues.apache.org/jira/browse/DBCP-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz updated DBCP-372: ----------------------------- Fix Version/s: 1.4.1 > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira