Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326272 - Dedlock when starting Eclipse and waiting for all EJB-Validators finished
Summary: Dedlock when starting Eclipse and waiting for all EJB-Validators finished
Status: CLOSED DUPLICATE of bug 315286
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: jst.j2ee CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-27 03:40 EDT by Stefan Cordes CLA
Modified: 2010-10-25 06:07 EDT (History)
2 users (show)

See Also:


Attachments
Thread Dump from VisualVM (31.84 KB, text/plain)
2010-09-27 03:40 EDT, Stefan Cordes CLA
no flags Details
30 seconds earlier VisualVM Thread dump. (31.85 KB, text/plain)
2010-09-27 03:43 EDT, Stefan Cordes CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Cordes CLA 2010-09-27 03:40:11 EDT
Build Identifier: 20100218-1602

Sometimes when starting my workspace there are more than one Jobs in the Progress view at 0% with "starting validator for ....".

Attached find Thread-Dumps taken with VisualVM.
(4 Validator were waiting in the Progress View).


Reproducible: Sometimes

Steps to Reproduce:
1. Start Eclipse with approx 60 Projects (20 of them EJB-Projects)
Comment 1 Stefan Cordes CLA 2010-09-27 03:40:49 EDT
Created attachment 179605 [details]
Thread Dump from VisualVM
Comment 2 Stefan Cordes CLA 2010-09-27 03:43:14 EDT
Created attachment 179606 [details]
30 seconds earlier VisualVM Thread dump.

No progress in Eclipse: (Diff of 30 Seconds delayed thread dumps):
 9:42:13,23 C:\TEMP>fc t1.txt t2.txt
Comparing files t1.txt and T2.TXT
***** t1.txt

2010-09-27 09:08:27
Full thread dump Java HotSpot(TM) Client VM (17.0-b17 mixed mode, sharing):
***** T2.TXT

2010-09-27 09:08:03
Full thread dump Java HotSpot(TM) Client VM (17.0-b17 mixed mode, sharing):
*****

***** t1.txt

"Attach Listener" daemon prio=10 tid=0x03236c00 nid=0x854 runnable [0x00000000]
   java.lang.Thread.State: RUNNABLE
***** T2.TXT

"Attach Listener" daemon prio=10 tid=0x03236c00 nid=0x854 waiting on condition [0x00000000]
   java.lang.Thread.State: RUNNABLE
*****

***** t1.txt

JNI global references: 1724

***** T2.TXT

JNI global references: 1723

*****
Comment 3 Ayushman Jain CLA 2010-09-27 04:45:23 EDT
Not a JDT/Core issue. Moving to web tools for comment.
Comment 4 Kaloyan Raev CLA 2010-09-28 06:16:32 EDT
Looks like a problem in the J2EE EMF models. Perhaps, thread "Worker-21" is the problematic one. 

Unfortunately, I am not quite familiar with these models. Could some of the other JEE Tools committers take a look?
Comment 5 Carl Anderson CLA 2010-09-28 09:43:39 EDT
You seem to have encountered bug 315286 which, unfortunately, was fixed in WTP 3.2.1, while you are using WTP 3.1.2 (guessing from your build identifier).  The EMF models are attempting to initialize each other in a non-thread-safe way.

We just announced Helios SR1, which contains the fix for your issue.  I would highly recommend using that, if at all possible.

*** This bug has been marked as a duplicate of bug 315286 ***
Comment 6 Stefan Cordes CLA 2010-10-25 06:07:10 EDT
Still happens with
Version: Helios Service Release 1
Build id: 20100917-0705