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] [Updated] (DERBY-6669) Transactional integrity not maintained properly in multi-threaded system
Date Wed, 30 Jul 2014 22:16:41 GMT

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

Karl Wright updated DERBY-6669:

    Attachment: manifoldcf.log

This is the annotated manifoldcf.log.  I have not correlated back to derby.log queries; hopefully
the timestamps will make that straightforward.

The part of the test that fails is annotated beginning at the first >>> in the file.
 The records that are messed up are JOBQUEUE table records with id's 1406755305836 and 1406755305835.
 See all annotation comments beginning with ">>>" for explanation of what I believe
is incorrect behavior.  Bear in mind that these records are accessed in a transaction with
FOR UPDATE both explicitly (with id=xxx queries) and implicitly (with some other query criteria).
 The threads involved for the 836 record are worker thread 20 (and its helper threads) as
well as worker thread 17 (and its helper threads).  Please let me know if you need any clarification.

> 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:,
>         Environment: Windows; not clear if the same failure will occur on Linux or not,
timing seems to be critically important.
>            Reporter: Karl Wright
>         Attachments: DERBY-6669.zip, manifoldcf.log
> 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

View raw message