Community
Participate
Working Groups
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.
Created attachment 178209 [details] javadump while hung at "waiting for background job to comlete"
Oh, and I should say ... this was on recent I build on WTP 3.3, circa 9/4/2010.
Looks more like an issue with the Java EE dependency graph and maybe the JAXWS tests. Our thread's just waiting.
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 ***