You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Valentin Mahrwald (JIRA)" <ji...@apache.org> on 2011/02/04 14:53:28 UTC

[jira] Resolved: (ARIES-390) Deadlock in Blueprint service lookup

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

Valentin Mahrwald resolved ARIES-390.
-------------------------------------

    Resolution: Fixed

Changes committed in #990185.

> Deadlock in Blueprint service lookup
> ------------------------------------
>
>                 Key: ARIES-390
>                 URL: https://issues.apache.org/jira/browse/ARIES-390
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: 0.2
>            Reporter: Valentin Mahrwald
>            Assignee: Valentin Mahrwald
>             Fix For: 0.3
>
>
> As described in https://issues.apache.org/jira/browse/GERONIMO-5554 there is potential deadlock in the Blueprint service code.
> In particular, ServiceRecipe has a lock hierarchy of getting an instance lock on the ServiceRecipe instance and then getting the Blueprint container-wide lock for the blueprint repository. However, while the blueprint container is creating its instances a thread may also come into the ServiceRecipe lookup code already having the blueprint repository lock.
> In such a case deadlock is possible because two threads can attempt to obtain the lock in either order.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira