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.
Product Version = NetBeans IDE Dev (Build 201606270002) Operating System = Mac OS X version 10.11.4 running on x86_64 Java; VM; Vendor = 1.8.0_92 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.92-b14 Reproducibility: Happens every time STEPS: * Open or create Java Web project. Using Maven web in this case. * Edit a JSP fragment * Note `Scanning Facelets libraries...` process starts. ACTUAL: Scanning Facelets libraries... process starts and never completes. This prevents any other inspected process from executing such as navigate sources or code completion. EXPECTED: Process should exit quickly. Note that the project in question does not use facelets and is Spring/MVC + Apache Tiles 3 based with knockout.js. NOTE Ignore the maven exceptions in the log, a car just hit a power pole where I work and the servers are not reachable
Created attachment 160170 [details] IDE log
We need more details about this as I'm not able to reproduce. Perhaps it is related to unreachable servers or some particular library or both. Would be good to have reproducible use case. Also please provide a thread dump (http://wiki.netbeans.org/GenerateThreadDump) for the situation when scanning is stucked. Anything would help...
Created attachment 160298 [details] thread dump while 'scanning facelets libraries' is never finishing
I am running current netbeans nightly (as of 20160707) and this issue pops up without fail after netbeans has been running for a while (30 mins or even sooner). Am attaching a thread dump. Please contact me to run any experimental patches if required.
Created attachment 160314 [details] NetBeans sdtout log with thread-dump This is the standard output from the IDE of a session where this occurred, this only contains the thread dump. Using dev 201607070002
Created attachment 160315 [details] NetBeans stderr log This is the error output from the IDE of a session where this occurred. This is relevant as many exceptions are present which look related to the cause. Using dev 201607070002
the trigger for this seems to be an updated related lib. In my case I have updated from Shiro 1.2.5 to Shiro 1.2.6 when the scan started. Potential workaround: I deleted the complete folder ~/.m2/repository/org/apache/shiro while IDE was shutdown. When Netbeans then reloaded the library (only 1.2.6 the scan did not appear again)
(In reply to jomu from comment #7) > the trigger for this seems to be an updated related lib. In my case I have > updated from Shiro 1.2.5 to Shiro 1.2.6 when the scan started. > > Potential workaround: I deleted the complete folder > ~/.m2/repository/org/apache/shiro while IDE was shutdown. When Netbeans > then reloaded the library (only 1.2.6 the scan did not appear again) Somewhat strange enough you are actually onto something. I'm not willing to delete my entire local maven repository cache as it's 4GB containing local copies of atlassian products and libraries. I have however moved the repository out of the way and the problem does appear to have ceased. Note, I do not have a copy of shiro anywhere in my prior repository cache.
From my point of view it does not need to be Shiro but can be any other faclet related library you use and then update. And it should be enough (for the workaround) to clean / remove only that portion of the repository.
(In reply to jomu from comment #9) > From my point of view it does not need to be Shiro but can be any other > faclet related library you use and then update. And it should be enough (for > the workaround) to clean / remove only that portion of the repository. Agreed, though the trick is trying to work out which dependency IS causing the error, and I update mine frequently using the `versions:show-dependency-updates` mojo. I presently have 4,435 artefacts in my repository which would be tricky to work out which ones are causing the problem. What's strange though is why NB would be looking at any dependency that's not directly or transiently referenced by the current open project(s).
This was caused by the fix for issue #251571. I reverted part of it. So this one should be fixed. I'm not going to reopen #251571 as the remaining part should be good enough anyway though I'll look at it again. web-main 1be7d42cb940
Integrated into 'main-silver', will be available in build *201607130002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/1be7d42cb940 User: Petr Hejl <phejl@netbeans.org> Log: #262583 - [regression] Editing JSP content starts `Scanning Facelets libraries...` indefinitely
*** Bug 262376 has been marked as a duplicate of this bug. ***