commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DBCP-407) PoolablePreparedStatement invalidated because of non cleared batch
Date Tue, 24 Feb 2015 03:23:31 GMT

     [ https://issues.apache.org/jira/browse/DBCP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Phil Steitz closed DBCP-407.
----------------------------

> 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.3.4#6332)

Mime
View raw message