db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4928) Deadlock-prone synchronization in BasicDependencyManager
Date Mon, 06 Dec 2010 16:38:11 GMT

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

Kristian Waagan updated DERBY-4928:

    Issue & fix info: [Patch Available]

> 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