No idea how to reproduce. I had been trying the Calculator sample apps using GFv3. They seemed to hang during the deployment build; I tried to stop the builds without success. When I tried to shut down the IDE, it just froze.
Created attachment 93139 [details]
Thread dump of deadlock
Created attachment 93140 [details]
Happened to me again after killing & restarting IDE. I ran Calculator app pair - all worked. Then I closed these and made a RESTful Hello World sample and tried to run that (without restarting GF). Hung during Ant build; Run > Stop Build showed "aborted" in the OW but the OW tab did not close; and closing IDE failed. Still unsure how to reproduce from scratch, however.
Lots of EJB classes in this thread dump - Andrey, can you please investigate?
re. "Lots of EJB classes in this thread dump" - issue 182811 will address problem with too many requests in default RequestProcessor from EjbsNodeFactory.
The problem is that WebAppMetadataModelImpl.getMetadata is blocking task "Parsing & Indexing Loop" from finishing because it posted runnable to default request processor but queue of default RP is full of EjbsNodeFactory tasks which wait back on parsing task. Fixing issue 182811 may (if not resolve this) make this deadlock less frequent. But real cause might be in org.netbeans.modules.web.jsf.editor.index.JsfIndexer$Factory.scanFinished(JsfIndexer.java:136) which should perhaps execute its job to its own thread and not in "Parsing and Indexing Look"? Passing to Marek to have a evaluate.
(In reply to comment #5)
> make this deadlock less frequent. But real cause might be in
> which should perhaps execute its job to its own thread and not in "Parsing and
> Indexing Look"? Passing to Marek to have a evaluate.
This cannot happen after January 14th - see e9caef8c3002 and the already fixed Bug 179456 - Parsing infrastructure locked during startup with JSF files
*** This bug has been marked as a duplicate of bug 179456 ***