[
https://issues.apache.org/jira/browse/DERBY-6727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-6727:
--------------------------------------
Attachment: DERBY-6727.diff
Attaching a patch that adds two test cases that fork a jvm process so that it
mimics 'crashing' the jvm (actually not crashing).
The test that actually tests DERBY-5165 are still disabled by prefixing an 'x'
to the test name.
Ready for review.
> 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
> 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)
