Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 5 Dec 2011 13:11:41 +0000 (UTC)
From: "Naozumi Taromaru (Created) (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <901363802.41062.1323090701066.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (DBCP-372) Statement Leak occurs when batch update
 is used.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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.4, 1.3
         Environment: Oracle 11g
            Reporter: Naozumi Taromaru
            Priority: Critical


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