You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/09/16 18:45:34 UTC

[jira] [Resolved] (DERBY-6727) test behavior of open XA transactions when the database is crashed (not just shutdown)

     [ https://issues.apache.org/jira/browse/DERBY-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren resolved DERBY-6727.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 10.12.0.0

The nightly tests appeared clean after this check-in except for the failures which are attributed to DERBY-6699. Resolving.

> test behavior of open XA transactions when the database is crashed (not just shutdown)
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-6727
>                 URL: https://issues.apache.org/jira/browse/DERBY-6727
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.12.0.0
>
>         Attachments: DERBY-6727.diff
>
>
> DERBY-5165 reflects a problem where after shutdown of a database with an open XA transaction with update changes uncommitted, it appears as if the locks are released when the database is available again. Instead, locks should be kept and subsequent reads should time-out.
> It would be nice to have a test case that tests the behavior of an open XA transaction when the jvm/thread with the transaction is killed/interrupted, rather than it doing an (orderly) database shutdown.



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