[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-622) Deadlock in Module FallbackClassLoader

[Steve Reed (JIRA)]

     [ https://issues.jboss.org/browse/JBOSGI-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Reed updated JBOSGI-622:
------------------------------

    Attachment: jboss-dead-lock.txt


Thread Dump from JBoss-AS. Has deadlock details.
                
> Deadlock in Module FallbackClassLoader
> --------------------------------------
>
>                 Key: JBOSGI-622
>                 URL: https://issues.jboss.org/browse/JBOSGI-622
>             Project: JBoss OSGi
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Blueprint
>    Affects Versions: JBossOSGi 2.0.0
>            Reporter: Steve Reed
>            Assignee: Thomas Diesler
>         Attachments: jboss-dead-lock.txt
>
>
> Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar
> Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8abc6e07748
> During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started. 
> The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible.
> I will attach the thread dump to this issue as supporting evidence.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira