This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 104831 - Scanning never ends
Summary: Scanning never ends
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Jan Lahoda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-25 12:23 UTC by Peter Zavadsky
Modified: 2007-05-28 10:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
thread dump (excludeding huge amount of NBSwingWorker threads) (19.73 KB, text/plain)
2007-05-25 12:29 UTC, Peter Zavadsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Zavadsky 2007-05-25 12:23:41 UTC
It started today (I use private builds made from up-to-date sources each
morning), steps to reproduce:
1) Get build containing VW (e.g. do build-nozip + build-vw).
2) Start it with clean userdir
3) Open visualweb/designer project
4) The scanning starts and at certain point it goes into neverending loop,
showing message:
"Compiling <nb_source_path>/websvc/jaxwsmodel/src"
That message never gets away, and the scanning never finishes, thus all
depending services are unavailable.
Comment 1 Peter Zavadsky 2007-05-25 12:24:41 UTC
There was no exception neither shown nor logged.
Comment 2 Peter Zavadsky 2007-05-25 12:29:26 UTC
Created attachment 42783 [details]
thread dump (excludeding huge amount of NBSwingWorker threads)
Comment 3 Erno Mononen 2007-05-25 16:00:36 UTC
Happened to me as well (with an old user dir) with the latest nightly build, 
had several NB module projects open and after about 20 mins the scanning was 
still in progress (also in websvc/jaxmodel). At that point I made the mistake 
of trying to refactor a variable, causing the IDE to stop responding 
completely. IMO a P1.
Comment 4 Jan Lahoda 2007-05-28 09:09:54 UTC
Cause known. Should be fixed soon.
Comment 5 Jan Lahoda 2007-05-28 10:49:12 UTC
Should be fixed now:
Checking in javac-impl.jar;
/cvs/java/external/javac-impl.jar,v  <--  javac-impl.jar
new revision: 1.52; previous revision: 1.51
done