db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guy Pardon (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5165) Prepared XA transaction locks are not kept across DB restart
Date Thu, 31 Mar 2011 13:23:06 GMT
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
    Affects Versions: 10.6.2.1
         Environment: Mac OSX 
            Reporter: Guy Pardon


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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message