[DERBY-2220] Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.2.0, 10.3.1.4
• Fix Version/s: 10.2.2.1, 10.3.1.4
• Component/s: JDBC
• Environment: Solaris Nevada build 49, Sun's JDK1.6
• Urgency: Normal
• Assignee: Julius Stroffek
• Reporter: Julius Stroffek
• Created: 08/Jan/07 13:16
• Updated: 25/Jul/08 17:36
• Resolved: 23/Mar/07 07:37

Description

Using this piece of code derby will not release a table lock of 'dummy' table.

String query = "insert into dummy (field1) values ('" + Integer.toString(value) + "')";
XAConnection xaConnection = createXAConnection("jdbc:derby://localhost:1527/TestDB", "", "");
XAResource xaResource = xaConnection.getXAResource();
conn = xaConnection.getConnection();

Xid xid = createXid(value);

xaResource.setTransactionTimeout(10);
xaResource.start(xid, XAResource.TMNOFLAGS);

Statement statement = conn.createStatement();
statement.execute(query);

// terminate the client application
// this will not release any locks
System.exit(0);