[DERBY-638] Network driver setTransactionIsolation() causes a commit, but does not complete it locally

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.3.1, 10.2.1.6, 10.3.1.4
• Fix Version/s: 10.1.3.2, 10.2.2.0, 10.3.1.4
• Component/s: Network Client
• Assignee: Bernt Johnsen
• Reporter: Deepa
• Created: 22/Oct/05 03:33
• Updated: 13/Dec/07 09:04
• Resolved: 16/Nov/06 12:24

Description

When autocommit is set to false, a call to setTransactionIsolation using client driver does not end the transaction when the method exits. When a close() is called on the conection, it throws an exception.

Running the code below:

conn.setAutoCommit(false);
conn.setTransactionIsolation(Connection.TRANSACTION_READ_COMMITTED);
try

{ conn.close(); }

catch(SQLException se)

{ System.out.println("Got exception when closing the connection"); se.printStackTrace(); }

with client driver gives:
Got exception when closing the connection
org.apache.derby.client.am.SqlException: java.sql.Connection.close() requested while a transaction is in progress on the connection.The transaction remains active, and the connection cannot be closed.

with embedded driver, it works okay and does not throw any exception.

Issue Links

• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• is related to: DERBY-2084 getTransactionIsolation() in network client should not activate a transaction
• relates to: DERBY-2064 Network client setTransactionIsolation() commits any active transactions