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 21:40:38 GMT

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

Karl Wright updated DERBY-6669:
-------------------------------

    Attachment: DERBY-6669.zip

This is a *different* run of the test case.

Included are the manifoldcf logs (which include all queries and also other information), the
derby.log, and the derby database (in the dbname directory).

I have not yet annotated the MCF log to find the precise failure queries.  That will take
some time, and I will attach an edited MCF log when done.


> 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
>         Attachments: DERBY-6669.zip
>
>
> 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