db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6669) Transactional integrity not maintained properly in multi-threaded system
Date Mon, 28 Jul 2014 16:17:39 GMT

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

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

I'd like to further point out that this particular failure was detected after literally years
of Derby usage by ManifoldCF.  It seems to require rather special conditions.  I therefore
very much doubt that it would be easy to reproduce in a trivial scenario.

I too am involved in release preparations at this time, but if it is essential I could probably
write a log replayer application that would digest a ManifoldCF database log and fire off
the appropriate queries.  Not sure what this buys, but it would be the most reliable way of
guaranteeing that we have a reproducible scenario without much additional code.

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