You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Steeve Beroard (JIRA)" <ji...@apache.org> on 2013/12/03 15:29:36 UTC

[jira] [Created] (DBCP-407) PoolablePreparedStatement invalidated because of non cleared batch

Steeve Beroard created DBCP-407:
-----------------------------------

             Summary: PoolablePreparedStatement invalidated because of non cleared batch
                 Key: DBCP-407
                 URL: https://issues.apache.org/jira/browse/DBCP-407
             Project: Commons Dbcp
          Issue Type: Bug
            Reporter: Steeve Beroard
            Priority: Minor


In PoolablePreparedStatement, passivate() method:
The first thing in this method is to consider the statement as closed. But then, if a batch has been added, the clearBatch() method is called.
That call is delegated to DelegatingStatement that send an SQLException because Statement is already considered as closed.
Then the statement is removed from the pool cache because of this so the cache is useless.
Maybe it should be better to get the innermost delegate in passivate() and then call clearBatch() on the underlying statement?



--
This message was sent by Atlassian JIRA
(v6.1#6144)