[jboss-jira] [JBoss JIRA] (AS7-6238) Deadlock in Module FallbackClassLoader

[Thomas Diesler (JIRA)]

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

Thomas Diesler moved JBOSGI-623 to AS7-6238:
--------------------------------------------

          Project: Application Server 7  (was: JBoss OSGi)
              Key: AS7-6238  (was: JBOSGI-623)
         Workflow: GIT Pull Request workflow   (was: jira)
      Component/s: OSGi
                       (was: Core Framework)
         Security:     (was: Public)
    Fix Version/s: 7.2.0.Alpha1
                       (was: JBossOSGi 1.2.0)

    
> Deadlock in Module FallbackClassLoader
> --------------------------------------
>
>                 Key: AS7-6238
>                 URL: https://issues.jboss.org/browse/AS7-6238
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: OSGi
>            Reporter: Steve Reed
>            Assignee: Thomas Diesler
>            Priority: Critical
>             Fix For: 7.2.0.Alpha1
>
>         Attachments: jboss-dead-lock.txt, ThreadDump-2.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