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.
Build: NetBeans IDE Dev (Build nbms-and-javadoc-6328-on-101215) VM: Java HotSpot(TM) Client VM, 17.1-b03, Java(TM) SE Runtime Environment, 1.6.0_22-b04 OS: Windows 7 User Comments: aquaglia: Opening Maven dependency details lmorissette: occured while attempting to view dependency properties for xom stopd: Checked out ant 1.7.1 sources from subversion and opened the project. Exception occured when I tried to open the maven dependency graph for the main project. jsacha: ? Stacktrace: java.lang.AssertionError at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.loadIndexingContext(NexusRepositoryIndexerImpl.java:263) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.access$400(NexusRepositoryIndexerImpl.java:161) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$8.run(NexusRepositoryIndexerImpl.java:802) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl$8.run(NexusRepositoryIndexerImpl.java:800) at org.openide.util.Mutex.writeAccess(Mutex.java:436) at org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl.getRecords(NexusRepositoryIndexerImpl.java:800)
Created attachment 104133 [details] stacktrace
Looks like a regression caused by per-repo mutex? Not obvious how it could happen, but my guess is that getRepoMutex(String) should have been synchronized - perhaps there is a race condition whereby getRecords obtains one Mutex for a given repo, in parallel another thread calls getRepoMutex and stores its own Mutex there, and then loadIndexingContext is holding a lock on the wrong mutex.
This bug already has 10 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=173427
Last build in the list of reports is 110214. Resolving as a dup of fixed issue 195541 which got integrated on 110218. *** This bug has been marked as a duplicate of bug 195541 ***