db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6669) Transactional integrity not maintained properly in multi-threaded system
Date Thu, 17 Jul 2014 14:29:05 GMT

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

Rick Hillegas commented on DERBY-6669:
--------------------------------------

I haven't followed the link yet. But note that Derby does not support transaction isolation
via MVCC snapshots.

> Transactional integrity not maintained properly in multi-threaded system
> ------------------------------------------------------------------------
>
>                 Key: DERBY-6669
>                 URL: https://issues.apache.org/jira/browse/DERBY-6669
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.10.1.1, 10.10.2.0
>         Environment: Windows; not clear if the same failure will occur on Linux or not,
timing seems to be critically important.
>            Reporter: Karl Wright
>
> The Apache ManifoldCF project uses Derby for testing and small deployments.  We're seeing
a situation where transactional integrity is compromised.  This is while using MVCC mode.
 Please refer to CONNECTORS-998 for complete details, as well as a test case you can run to
reproduce the problem.
> I am happy to run the failing example on the same hardware I used to generate the log,
if that would be helpful.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message