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 229862 - Deadlock between FaceletsLibrarySupport and WebAppMetadataModelImpl
Summary: Deadlock between FaceletsLibrarySupport and WebAppMetadataModelImpl
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF Editor (show other bugs)
Version: 7.3
Hardware: All All
: P2 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-16 13:53 UTC by daveo17
Modified: 2013-05-18 02:53 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 200705


Attachments
stacktrace (2.13 KB, text/plain)
2013-05-16 13:53 UTC, daveo17
Details

Note You need to log in before you can comment on or make changes to this bug.
Description daveo17 2013-05-16 13:53:13 UTC
This issue was reported manually by sdedic.
It already has 2 duplicates 


Build: NetBeans IDE 7.3 (Build 201302132200)
VM: Java HotSpot(TM) 64-Bit Server VM, 17.1-b03, Java(TM) SE Runtime Environment, 1.6.0_22-b04
OS: Windows 7

User Comments:
daveo17: Every time I pull a new version of a java system net bean's background scanning hangs at 99 or 100%.  Then it magically decides to finish. In the future, with no code changes, the background scans complete normally. No error are identified in the code.

I updated to JDK 1.7.2. I am using Windows 7 ultimate 64 bit with 8 gb ram.

I have exited and re-entered the IDE, rebooted my computer, and do not find a pattern.

I have waited hours for it to finish. This is wasting a lot of time. With the number of other reports of this error I am surprised at the lack of response to correct a serious issue.

eng.amrelbatal: when using from jsf core in any project,just restarting  netbeans it shows me scanning facelets libraries and it doesn't finish and stop all net beans functionality




Stacktrace: 
java.lang.Exception: Scan canceled.
   at java.lang.Thread.getStackTrace(Thread.java:1479)
   at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:125)
   at org.netbeans.modules.parsing.impl.indexing.LogContext.create(LogContext.java:118)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.scheduleFirer(PathRegistry.java:829)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.resetCacheAndFire(PathRegistry.java:822)
   at org.netbeans.modules.parsing.impl.indexing.PathRegistry.access$500(PathRegistry.java:86)
Comment 1 daveo17 2013-05-16 13:53:15 UTC
Created attachment 134520 [details]
stacktrace
Comment 2 Martin Fousek 2013-05-17 07:33:41 UTC
Deployment descriptor FO refresh (which is unfortunately probably necessary after changes in DD version/type definitions) invokes refresh into the FaceletsLibrarySupport. And it is stuck there since in the meantime editor invoked getting facelets libraries which wasn't finished due to call back to the DD. I moved the FLS's invalidateLibrariesCache() into BG thread which should resolve this.

Fixed in web-main #7482eccf216c.
Comment 3 Quality Engineering 2013-05-18 02:53:17 UTC
Integrated into 'main-golden', will be available in build *201305172300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/7482eccf216c
User: Martin Fousek <marfous@netbeans.org>
Log: #229862 - Deadlock between FaceletsLibrarySupport and WebAppMetadataModelImpl