[DERBY-5915] "Cannot close a connection while a transaction is still active" when using PreparedStatement

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.9.1.0
• Component/s: JDBC
• Labels: derby_triage10_10
• Environment: java 1.6+windows 7
• Urgency: Urgent
• Assignee: Unassigned
• Reporter: David Chan
• Created: 31/Aug/12 14:07
• Updated: 25/Sep/12 16:21

Description

create a Preparedstatement, set its parameters, then execute it. Exception throwed when closing connection.
PreparedStatement file_stmt = conn.prepareStatement(OperationSql.NEW_FILE);
file_stmt.setString(1, rel_path);
file_stmt.setString(2, short_name);
file_stmt.setInt(3, INITIAL_VERSION);
int inserted = file_stmt.executeUpdate();
//System.out.println(inserted);
file_stmt.close();
conn.close();
Exception:
java.sql.SQLException: Cannot close a connection while a transaction is still active.
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.checkForTransactionInProgress(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.close(Unknown Source)

BTW, I want to use Derby as desktop db of a client application and found it is REALLY buggy!!

Issue Links

• relates to: DERBY-3806 java.sql.SQLException: Cannot close a connection while a transaction is still active thrown on Connection.close