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

Bug 324502

Summary:

Hang while "Configuring for JavaScript"

Product:

[WebTools] WTP Java EE Tools

Reporter:

David Williams <david_williams>

Component:

jst.j2ee

Assignee:

jst.j2ee <jst.j2ee-inbox>

Status:

CLOSED DUPLICATE

QA Contact:

Chuck Bridgham <cbridgha>

Severity:

normal

Priority:

CC:

ccc, cmjaun

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
javadump while hung at "waiting for background job to comlete"	none

Description David Williams

2010-09-03 22:05:51 EDT

While running some unit tests locally, I happened to notice once when the cfx tests were "hung". I'll attach a thread dump, but noticed that in the status? progress? area there was a message that said "Configuring for JavaScript". 

Before thinking to get the dump, I tried to exit the work bench, which then hung at the "saving workbench state" exit dialog, saying "waiting for background work to complete", and the background job was "Configuring for JavaScript". 
(Its this dialog in the "main" thread, I suspect ... so wouldn't pay too much attention to that ... it's supposed to wait there until background job is done). 

My guess is the original problem was similar, though ... with unit tests, workbenches are started and stopped many times, and suspect if "Configuring for JavaScript" hasn't completed yet, then the "shutdown" somehow conflicts with it, and hangs the system. 

Sorry I don't know more about these org.eclipse.jst.ws.cxf.tests , but they do hang (DNF) on build machines about once a week. 

So, just wanted to collect and document what little information I had.

Comment 1 David Williams

2010-09-03 22:07:01 EDT

Created attachment 178209 [details]
javadump while hung at "waiting for background job to comlete"

Comment 2 David Williams

2010-09-03 22:23:59 EDT

Oh, and I should say ... this was on  recent I build on WTP 3.3, circa 9/4/2010.

Comment 3 Nitin Dahyabhai

2011-06-30 15:20:20 EDT

Looks more like an issue with the Java EE dependency graph and maybe the JAXWS tests.  Our thread's just waiting.

Comment 4 Carl Anderson

2011-09-13 09:43:23 EDT

This appears to be the same sort of hang that occurred in the dependency graph, for which Jason Sholl put together a fix in bug 331719.  If this reoccurs, we can reopen this bug.

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