Deadlock in Module FallbackClassLoader -------------------------------------- Key: JBOSGI-623 URL: https://issues.jboss.org/browse/JBOSGI-623 Project: JBoss OSGi Issue Type: Bug Security Level: Public(Everyone can see) Components: Core Framework Reporter: Steve Reed Assignee: Thomas Diesler Priority: Critical Fix For: JBossOSGi 1.2.0 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/ed2bc551a55ec6a8167a8657cbb5d8... 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.