db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5165) Prepared XA transaction locks are not kept across DB restart
Date Fri, 31 Oct 2014 16:14:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191989#comment-14191989
] 

ASF subversion and git services commented on DERBY-5165:
--------------------------------------------------------

Commit 1635803 from mikem@apache.org in branch 'code/trunk'
[ https://svn.apache.org/r1635803 ]

DERBY-5165

Update code to reclaim locks on prepared but not committed XA transaction
update locks on recovery reboot following crash.  Enable checked in test
that demonstrated the bug, which was verified to fail before the change
and pass after the change.

> Prepared XA transaction locks are not kept across DB restart
> ------------------------------------------------------------
>
>                 Key: DERBY-5165
>                 URL: https://issues.apache.org/jira/browse/DERBY-5165
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.6.2.1
>         Environment: Mac OSX 
>            Reporter: Guy Pardon
>            Assignee: Mike Matrigali
>              Labels: derby_triage10_11
>         Attachments: DERBY-5165Test.diff, Derby5165.java
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message