Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/DERBY-8 Here is an overview of the issue: --------------------------------------------------------------------- Key: DERBY-8 Summary: Connection object gets created with un-supported holdability on getting Connection object from XAConnection "inside" the global transaction Type: Bug Status: Unassigned Priority: Minor Project: Derby Components: JDBC Versions: 10.0.2.0 Assignee: Reporter: Tulika Agrawal Created: Mon, 27 Sep 2004 6:00 PM Updated: Mon, 27 Sep 2004 6:00 PM Description: Reporting for Mamta Satoor, filed on Derby-dev list. I think there is a bug in Derby when the user code tries to get the Connection object from XAConnection "inside" the global transaction. In this case, the Connection object gets created with un-supported holdability. Look at the following piece of code and it's output to see what exactly happens EmbeddedXADataSource dscsx = new EmbeddedXADataSource(); dscsx.setDatabaseName("wombat"); XAConnection xac = dscsx.getXAConnection("fred", "wilma"); XAResource xr = xac.getXAResource(); xid = getXid(27, (byte) 21, (byte) 01); xr.start(xid, XAResource.TMNOFLAGS); conn1 = xac.getConnection(); System.out.println("This is a bug. Connection's holdability should have been CLOSE_CURSORS_AT_COMMIT since it is in the global transaction"); System.out.println("CONNECTION(in xa transaction) HOLDABILITY " + (conn1.getHoldability() == ResultSet.HOLD_CURSORS_OVER_COMMIT)); System.out.println("Autocommit on Connection inside global transaction has been set correctly to " + conn1.getAutoCommit()); xr.end(xid, XAResource.TMSUCCESS); The output for the above piece of code is This is a bug. Connection's holdability should have been CLOSE_CURSORS_AT_COMMIT since it is in the global transaction CONNECTION(in xa transaction) HOLDABILITY true Autocommit on Connection inside global transaction has been set correctly to false --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
