Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <6677570.130491291653491102.JavaMail.jira@thor>
Date: Mon, 6 Dec 2010 11:38:11 -0500 (EST)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4928) Deadlock-prone synchronization in
 BasicDependencyManager
In-Reply-To: <8961587.73021291297630638.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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: 10.8.0.0
>            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.