db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6669) Transactional integrity not maintained properly in multi-threaded system
Date Wed, 30 Jul 2014 18:52:38 GMT

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

Mike Matrigali commented on DERBY-6669:
---------------------------------------

scanned through the log provided with does have some queries.  It may be all of them, not
sure as it is not a derby.log.  

There are deadlocks involved which may or may not be of interest.  Need to make sure application
understands that on deadlock derby will backout multi-statment transaction and release all
locks.  On retry needs to repeat all steps of the transaction.  

With a derby.log would be able to verify autocommit vs multi-statement transactions.  

> 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