Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361129

Summary: Deadlock between main thread and Eclipse Blueprint Extender Thread
Product: [Eclipse Project] Equinox Reporter: Reto Urfer <reto.urfer>
Component: FrameworkAssignee: equinox.framework-inbox <equinox.framework-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: tjwatson
Version: 3.7.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Stack trace of the two threads which lock each other none

Description Reto Urfer CLA 2011-10-17 09:00:32 EDT 
Build Identifier: 3.7.1

It seems that the deadlock was introduced with the WeavingHookConfigurator and the WovenClassImpl. The WovenClassImpl tries to access the service registry and has already locked the default DefaultClassLoader.

Reproducible: Sometimes

Steps to Reproduce:
It depends on the timing between the different threads but currently i am not able to start our application with a Eclipse 3.7.1 target platform
Comment 1 Reto Urfer CLA 2011-10-17 09:01:45 EDT 
Created attachment 205317 [details]
Stack trace of the two threads which lock each other
Comment 2 Thomas Watson CLA 2011-10-17 10:14:52 EDT 

*** This bug has been marked as a duplicate of bug 359535 ***
Comment 3 Thomas Watson CLA 2011-10-17 10:16:21 EDT 
It would be interesting to know if you can reproduce this on Java 7.