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 Wed, 30 Jul 2014 18:56:39 GMT

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

Karl Wright commented on DERBY-6669:

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

It is complete.

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

Yes, the application is well aware of that.  It may be, though, that the deadlock release
of locks also releases locks held by other threads.  All application threads, if their locks
are released, should receive a sql exception of some kind; if that doesn't happen, they have
no idea what happened.

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