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 262413 - NB 8.1 freeze
Summary: NB 8.1 freeze
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: Web Project (show other bugs)
Version: 8.1
Hardware: PC Other
: P2 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-13 14:56 UTC by ecerichter
Modified: 2016-06-17 01:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump on frozen NB (66.61 KB, text/plain)
2016-06-13 14:56 UTC, ecerichter 		Details
NetBeans log file (878.14 KB, application/octet-stream)
2016-06-13 14:57 UTC, ecerichter 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ecerichter 2016-06-13 14:56:09 UTC 
Created attachment 160038 [details]
Thread dump on frozen NB

After a long while (more than a year), I've faced a first NB 8.1 freeze (that is rock solid, I must say).

Environment:
- NB 8.1 with all updates
- Oracle JDK 1.8.0_91 x64
- Win Server 2008r2 with all updates
- BitDefender endpoint security for servers (it never had any influence)
- Latest GWT plugin (which is very important in this project)

What I was doing:
- I've commited all changes and closed a subversion versioned project
- Open a clone of the project that is in differente stage of development (kind of branch, but I just checkout the project in another folder without creating a new branch - I'll manually merge all changes after all) - in a different folder, of course
- Executed a subversion "update to head" to get all current changes
- Solved all conflicts
- Execute a "Clean" to do a start from scratch

NB fronzen with "Checking for external changes" in state "suspended".
I've immediately opened a jVisualVM and took the thread dump (attached to this issue), and also the netbeans log.
Comment 1 ecerichter 2016-06-13 14:57:21 UTC 
Created attachment 160039 [details]
NetBeans log file
Comment 2 Tomas Zezula 2016-06-15 15:54:49 UTC 
The problem is in JavaEEWSOpenHook.WS_REQUEST_PROCESSOR which tries to acquire project mutex in exclusive mode in JavaEEWSOpenHook$WebservicesChangeListener:284 in parsing task (holds parser lock).
However the project mutex is held by the ProjectProperties.PP.RP (shared mode) trying to acquire parsing lock WebAppMetadataModelImpl.runReadAction(WebAppMetadataModelImpl.java:133)
Comment 3 Tomas Zezula 2016-06-15 15:56:55 UTC 
It's not a good idea trying to acquire project lock in exclusive mode under parser lock. Either reschedule the task or split the code into parser part and project store part.
Comment 4 Petr Hejl 2016-06-16 13:28:11 UTC 
Fixed in web-main ca7b6e0318a6.
Comment 5 Quality Engineering 2016-06-17 01:52:03 UTC 
Integrated into 'main-silver', will be available in build *201606170002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/ca7b6e0318a6
User: Petr Hejl <phejl@netbeans.org>
Log: #262413 - NB 8.1 freeze