db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2531) client returns different connection on s.getConnection() on a statement obtained from a ConnectionPoolDataSource or XADataSource than the original connection.
Date Mon, 09 Apr 2007 05:52:32 GMT
client returns different connection on s.getConnection() on a statement obtained from a ConnectionPoolDataSource
or XADataSource than the original connection.
--------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: DERBY-2531
                 URL: https://issues.apache.org/jira/browse/DERBY-2531
             Project: Derby
          Issue Type: Bug
          Components: Network Client
    Affects Versions: 10.3.0.0
            Reporter: Myrna van Lunteren


In the following scenario:                

        ClientXADataSource dsx = new ClientXADataSource();
        dsx.setDatabaseName(dbName);
        XAConnection xac = dsx.getXAConnection();
        XAResource xar = xac.getXAResource();

        Connection cs1 = xac.getConnection();
        Statement sru1 = cs1.createStatement();
        sru1.setCursorName("SN1");
        sru1.executeUpdate("insert into intTable values 1,2,3");
        Connection conn2 = s.getConnection();

When using an EmbeddedXADataSource, cs1 and conn2 are the same connection. However with Client
they're not.

Found during conversion of test checkDataSource to DataSourceTest.java.
If this difference is correct, or acceptable, it should get documented...


With DerbyNetClient, they're not the same.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message