db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4928) Deadlock-prone synchronization in BasicDependencyManager
Date Wed, 08 Dec 2010 10:46:01 GMT

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

Knut Anders Hatlen commented on DERBY-4928:

Looks like a good cleanup to me. +1
(One small typo in a comment in BaseJDBCTestCase: "Run throgh" -> "Run through")

> Deadlock-prone synchronization in BasicDependencyManager
> --------------------------------------------------------
>                 Key: DERBY-4928
>                 URL: https://issues.apache.org/jira/browse/DERBY-4928
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-4928-1a-depman_sync_and_cleanup.diff
> The synchronization in BasicDependencyManager is prone to deadlock, because database
locks are obtained while holding the monitor on "this".
> Problem observed when testing the automatic index statistics update prototype.
> There are comments in the file suggesting that in-memory dependencies should be accessed
while holding the Java monitor, but the monitor should not be held when accessing stored dependencies.
The implementation is breaking this rule/suggestion.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message