You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2009/01/20 23:04:59 UTC

[jira] Closed: (FELIX-891) Bundle lock acquisition should not record lock until it verifies the bundle is lockable

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

Richard S. Hall closed FELIX-891.
---------------------------------

    Resolution: Fixed

Fixed in trunk.

> Bundle lock acquisition should not record lock until it verifies the bundle is lockable
> ---------------------------------------------------------------------------------------
>
>                 Key: FELIX-891
>                 URL: https://issues.apache.org/jira/browse/FELIX-891
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: felix-1.4.1
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: felix-1.6.0
>
>
> Felix 1.4.1 introduced a global bundle lock for multi-bundle refresh/resolve operations. The acquireBundleLock() was modified to record which bundles were holding bundle locks, but it does so improperly. As long as the global lock is free, it records the calling thread as acquiring its requested lock, then it checks to see if the bundle is actually lockable and waits until it is. It should not record the calling thread as acquiring its requested lock until after it verifies the bundle is lockable.

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