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 "Karl Wright (JIRA)" <ji...@apache.org> on 2014/07/17 13:51:04 UTC

[jira] [Commented] (DERBY-6669) Transactional integrity not maintained properly in multi-threaded system

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

Karl Wright commented on DERBY-6669:
------------------------------------

Also: this test works properly on the other three databases MCF supports: PostgreSQL, MySQL, and HSQLDB, so I have some confidence that it's not just a minor coding issue.


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