[DERBY-2432] Unimplemented transaction time out for XA transactions may cause that locks will not be released when client terminates outside a unit of work.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 10.3.1.4
• Component/s: JDBC
• Urgency: Normal
• Assignee: Julius Stroffek
• Reporter: Julius Stroffek
• Created: 09/Mar/07 16:09
• Updated: 01/Jul/09 00:34
• Resolved: 15/Jun/07 13:23

Description

The XAResource interface provides function setTransactionTimeout which is currently not supported in derby.

When client application uses client driver to connect to derby database and the application crashes outside the unit of work of XA transaction and the transaction is not committed or rolled back yet the locks held by the transaction will not be released.

Issue Links

• relates to: DERBY-2849 Add a documentation for derby.jdbc.xaTransactionTimeout system/database property

Sub-Tasks

• Implement the XA transaction timeout support for embedded driver.: Closed
• Implement the XA transaction timeout support for client driver.: Closed