[DBCP-407] PoolablePreparedStatement invalidated because of non cleared batch

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Steeve Beroard
• Created: 03/Dec/13 14:29
• Updated: 24/Feb/15 03:23
• Resolved: 03/Feb/14 23:37

Description

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?

Issue Links

• duplicates: DBCP-372 Statement Leak occurs when batch update is used.