[ http://issues.apache.org/jira/browse/DERBY-638?page=all ]
Bernt M. Johnsen updated DERBY-638:
-----------------------------------
Attachment: DERBY-638.diff
Simple patch for this case. Ideally setTransactionIsolation should have been
done with some DRDA mechanism piggybacking the next query/update and (e.g. like
setQueryTimeout were done), but this would do as long as we're using
statement.execute("SET CURRENT ISOLATION...");
> setTransactionIsolation behaviour in network client driver is different from
> that of embedded driver
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-638
> URL: http://issues.apache.org/jira/browse/DERBY-638
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.2.1.6
> Reporter: Deepa Remesh
> Assigned To: Bernt M. Johnsen
> Attachments: d638.java, DERBY-638.diff
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
