db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernt M. Johnsen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-638) Network driver setTransactionIsolation() causes a commit, but does not complete it locally
Date Thu, 16 Nov 2006 12:10:38 GMT
     [ http://issues.apache.org/jira/browse/DERBY-638?page=all ]

Bernt M. Johnsen updated DERBY-638:
-----------------------------------

    Attachment: DERBY-638-v3-for-10.1.diff

Backport for 10.1 branch

> Network driver setTransactionIsolation() causes a commit, but does not complete it locally
> ------------------------------------------------------------------------------------------
>
>                 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, 10.1.3.1, 10.3.0.0
>            Reporter: Deepa Remesh
>         Assigned To: Bernt M. Johnsen
>             Fix For: 10.2.1.8, 10.3.0.0
>
>         Attachments: d638.java, d638_repro2.java, d638_repro3.java, DERBY-638-v2.diff,
DERBY-638-v3-for-10.1.diff, DERBY-638-v3.diff, DERBY-638-v3.stat, 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

        

Mime
View raw message