[jira] [Commented] (DERBY-5165) Prepared XA transaction locks are not kept across DB restart

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit 1622301 from [~myrna] in branch 'code/trunk'
[ https://svn.apache.org/r1622301 ]

DERBY-5165; Prepared XA transaction locks are not kept across DB restart
   Adding a test case (currently not enabled) based on the repro provided.

> 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)