[DERBY-4334] Invoking certain methods on PreparedStatements after the underlying connection changed forces repreparing

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.6.1.0
• Component/s: JDBC
• Labels: derby_triage10_5_2
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Tiago R. Espinha
• Created: 03/Aug/09 19:42
• Updated: 02/May/13 02:29

Description

Whenever we invoke methods like isClosed() or getMetaData() on prepared or callable statements after the underlying connection changed, these methods will try to reprepare the statement. This becomes an issue if in the meanwhile, the query became obsolete (e.g. querying a table that was dropped in the meanwhile).

For example, if we start a transaction and prepare a statement with "SELECT * FROM FOO;" then drop FOO with a parallel regular connection and try to invoke the said methods on the statement, a repreparement will be attempted. Since FOO no longer exists, it will throw an exception.

I fixed this issue on DERBY-4310 for the .close() calls on Prepared and Callable statements, but this will require more extensive work to convert the remaining methods that try to do a getRealStatement() on the XAStatementControl. I will be attaching a repro that pops this issue with the isClosed() call.

The approach I used in DERBY-4310 was to add a couple of methods to XAStatementControl that act directly on the real statement object and close them right away, without attempting to reprepare.

Issue Links

• is depended upon by: DERBY-5091 Derby Test and Fix 2011 GSoC Project
• relates to: DERBY-4310 Closing a prepared statement with an embedded XAConnection can cause the statement to be reprepared and errors related to missing dependencies. This can interfere with network server closeSession()