Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361129 - Deadlock between main thread and Eclipse Blueprint Extender Thread
Summary: Deadlock between main thread and Eclipse Blueprint Extender Thread
Status: CLOSED DUPLICATE of bug 359535
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.7.1   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-17 09:00 EDT by Reto Urfer CLA
Modified: 2011-10-17 10:16 EDT (History)
1 user (show)

See Also:

Attachments
Stack trace of the two threads which lock each other (8.36 KB, text/plain)
2011-10-17 09:01 EDT, Reto Urfer CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.