[DERBY-5165] Prepared XA transaction locks are not kept across DB restart

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.6.2.1
• Fix Version/s: 10.12.1.1
• Component/s: Store
• Labels: derby_backport_reject_10_11 derby_triage10_11
• Environment: Mac OSX
• Urgency: Urgent
• Issue & fix info: High Value Fix, Repro attached
• Bug behavior facts: Deviation from standard
• Assignee: Mike Matrigali
• Reporter: Guy Pardon
• Created: 31/Mar/11 13:22
• Updated: 09/Sep/16 09:52
• Resolved: 12/Dec/14 20:15

Description

Steps to reproduce:

1-perform update with XA, using, say Xid xid1
2-prepare xid1 with XA but do NOT commit
3-restart Derby DB
4-the updates of step 1 will be visible

When xid1 is rolled back after step 3 then the updates are gone. So my conclusion is that the transaction is not committed yet, but the updates are visible after prepare. This is a violation of the XA semantics.

Issue Links

• relates to: DERBY-6727 test behavior of open XA transactions when the database is crashed (not just shutdown)