aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Mahrwald (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ARIES-390) Deadlock in Blueprint service lookup
Date Fri, 03 Sep 2010 13:44:36 GMT

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

Valentin Mahrwald updated ARIES-390:
------------------------------------

    Fix Version/s: 0.3
                       (was: 0.2)

> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message