db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-638) setTransactionIsolation behaviour in network client driver is different from that of embedded driver
Date Fri, 21 Oct 2005 18:35:32 GMT
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
        Type: Bug
  Components: Network Client  
    Versions: 10.2.0.0    
    Reporter: Deepa Remesh


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