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

Bug 347966

Summary: Complete Eclipse Lockup After Project Creation/Refresh
Product: [WebTools] WTP Source Editing Reporter: Patric Rufflar <patric>
Component: jst.jspAssignee: jst.jsp <jst.jsp-inbox>
Status: CLOSED DUPLICATE QA Contact: Nick Sandonato <nsand.dev>
Severity: critical    
Priority: P3 CC: thatnitind
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
threaddump none

Description Patric Rufflar CLA 2011-06-01 11:40:24 EDT 
Build Identifier: 3.2.4

I noticed this behavior more than once:
I imported a project (using svn import), and after finishing checkout I do some changes in the project using an ant file, afterwards refreshing the project.

This resulted in a complete eclipse lockup, I had to kill the process.

I suppose that there's a conflict on the eclipse refresh mechanism and the JSPIndexManager.

For more details, please have a look at the thread dump



Reproducible: Sometimes
Comment 1 Patric Rufflar CLA 2011-06-01 11:41:00 EDT 
Created attachment 197106 [details]
threaddump
Comment 2 Patric Rufflar CLA 2011-06-01 11:46:31 EDT 
Additional information:
It's probably not a deadlock 
- CPU is utilized at maximum (by one thread) but eclipse did not return within 10 minutes - so I suppose an endless loop.
Comment 3 Nick Sandonato CLA 2011-06-01 13:31:33 EDT 
Hi Patric,

Would you mind supplying a couple additional thread dumps spaced out over time? JAX-WS is showing up in the dump too and appears to be holding onto the workspace lock. If it is the thread that is stuck in a loop, it might be blocking the JDT work being done in the UI thread. Subsequently, the JSP Index Manager would also be blocked.

A potential workaround may be disabling all the JAX-WS plug-ins (JAX-WS DOM Runtime and JAX-WS Utils) that are activated on startup via the preferences under General > Startup and Shutdown and restart the workbench.
Comment 4 Patric Rufflar CLA 2011-06-01 14:16:40 EDT 
Hi Nick,

I'll try to reproduce this issue to provide you additional thread dumps.
Maybe this bug is related to bug 347973 which occurred only one restart later (but didn't result in a total lockup).

Thanks for providing me the hint with a potential workaround.
Comment 5 Nick Sandonato CLA 2011-06-06 10:03:55 EDT 
Hey, Patric. Any luck with reproducing?

It sounds like this might be bug 347973, but this time it just happened to be going on while the JDT was doing some work for the Navigator.
Comment 6 Nick Sandonato CLA 2011-06-09 14:04:14 EDT 
Patric,

As far as I can tell, this is a duplicate of Bug 347973 but the index manager is just blocked waiting for the workspace lock. Thanks.

*** This bug has been marked as a duplicate of bug 347973 ***