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.
[ JDK VERSION : 1.6.0_07 ] Starting with build 200808060201, NetBeans is unable to open my project group anymore. The group does contain 35 maven2 projects (pom, jar, war artifacts), and the behaviour has successfully been reproduced in build 200808061401 both using an "old" and using a "clean" .netbeans configuration folder. After switching to this project group, the IDE doesn't lock up (menus are still responding, Options / Plugins / ... windows can be opened, most of the IDE ui still works even though slower than usually), but the "Opening group <group-name>" tasks comes just to 7 .. 9 %, stopping then until the IDE is closed via "Exit" (which successfully works, after asking to terminate the running "Open group..." task). Clicking the group task in the status bar, the project it seems stopping its work opening in is always different. Tried installing the updates pointed to in [1] without success. This one is related to [2] and [3] I guess, keeping it at lower priority, filing it again for the sake of completeness, thread dump to be attached. Thanks, Kristian [1] http://www.netbeans.org/issues/show_bug.cgi?id=142966 [2] http://www.netbeans.org/issues/show_bug.cgi?id=143021 [3] http://www.netbeans.org/issues/show_bug.cgi?id=143028
Created attachment 66749 [details] thread dump off recent build
no deadlock, it seems to be just happily running along.. was it taken at the time the changing groups process seemingly stopped? "org.netbeans.modules.project.ui.groups.GroupsMenu" daemon prio=10 tid=0x08383400 nid=0x36c7 runnable [0xafd04000..0xafd05040] java.lang.Thread.State: RUNNABLE at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:228) at java.io.File.isDirectory(File.java:754) at org.apache.maven.project.build.model.DefaultModelLineageBuilder.resolveParentPom(DefaultModelLineageBuilder.java:360) at org.apache.maven.project.build.model.DefaultModelLineageBuilder.buildModelLineage(DefaultModelLineageBuilder.java:131) at org.apache.maven.extension.DefaultBuildExtensionScanner.buildModelLineage(DefaultBuildExtensionScanner.java:425) at org.apache.maven.extension.DefaultBuildExtensionScanner.scanInternal(DefaultBuildExtensionScanner.java:137) at org.apache.maven.extension.DefaultBuildExtensionScanner.scanForBuildExtensions(DefaultBuildExtensionScanner.java:120) at org.apache.maven.embedder.MavenEmbedder.readProject(MavenEmbedder.java:377) at org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies_aroundBody0(MavenEmbedder.java:416) at org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies_aroundBody1$advice(MavenEmbedder.java:304) at org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies(MavenEmbedder.java:1) at org.netbeans.modules.maven.NbMavenProjectImpl.getOriginalMavenProject(NbMavenProjectImpl.java:208) - locked <0x71d24810> (a org.netbeans.modules.maven.NbMavenProjectImpl) at org.netbeans.modules.maven.NbMavenProjectImpl$Info.getDisplayName(NbMavenProjectImpl.java:658) at org.netbeans.modules.project.ui.groups.Group.progressMessage(Group.java:266) at org.netbeans.modules.project.ui.groups.DirectoryGroup.findProjects(DirectoryGroup.java:115) at org.netbeans.modules.project.ui.groups.Group.getProjects(Group.java:255) at org.netbeans.modules.project.ui.groups.Group.open(Group.java:319) at org.netbeans.modules.project.ui.groups.Group.setActiveGroup(Group.java:166) at org.netbeans.modules.project.ui.groups.GroupsMenu$2.run(GroupsMenu.java:208) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)
Yes. In this situation, I let a couple of minutes pass before taking the shot (the time required to write the issue report). Before that (this morning after installing and starting the new build using the "old" configuration folder), it remained around half an hour in this state (while I sorted my nightly inbox). No messages in messages.log, also; yesterday I read something in there more or less related to "re-syncing Eclipse projects" so I uninstalled the Eclipse Project Importer (some of my projects might contain old .project / .classpaths so I suspected this to be a problem); didn't change anything though. Is there anything else I can do tracking this?
does the tread dump change if you try multiple ones in sequence?
No change in the stack trace leaving it running for a while. But, after ignoring it again for more or less half an hour, the following happened: - OutOfMemoryError has been thrown (see attachment) - project group did open (most of the project seemed well at first sight, except for a couple of them marked as "badly formed maven2 projects". - closing and restarting the IDE: the group initially switched to seems open at startup, but no projects are opened. No sign that something is still happening.
Created attachment 66754 [details] OutOfMemoryError
(why does attaching things to this issue in my case change the target milestone from 6.5 to TBD?)
what sort of project group do you have? are the sources public (to allow me reproduce on the same data)? if not, what the the approximate size of the projects etc..
Hmmmmm.... Using a NetBeans 6.1 installment I just downloaded, the issue mainly seems to be caused by a mistake in the project structure introduced in yesterdays changes before the IDE mainly stopped being usable on the very project group (#143021): Two pom projects assigned to be "parent" of each other in a cyclic way... seems to bring the group loader to a grinding halt (and does explain the project being marked as "badly formed" after, finally, opening the project group). Fixing this in the project structure and trying to open the latest build again makes it work as desired again, also rendering #143021 and #143028 practically useless. Leaves the question however whether the plugin should deal better with project structure errors like this or if these errors are stupid/severe enough to not be dealt with in a meaningful way anyhow... /pondering/
I see. If you can extract a sample group of projects that demonstrates the problem, I suggest to file the issue against maven itself.
Created attachment 66784 [details] sample project group
simple test case see attached: Please... - ... unpack sample.tgz and open the projects in a recent NetBeans build, - ... "Clean and build" the "parent" project" which should end in parent-1 and parent-2 being built and installed, - ... open "parent-2"'s pom.xml and un-comment the "<parent>" tag, - ... save the changed pom.xml. The very moment (reproducibly tried with 200808061401) you do save the pom.xml, the IDE immediately becomes unresponsive, and, subsequently, whenever trying to start it opening these projects, ends up in the behaviour outlined earlier as well as in #143021 and #143028. Admittedly, using maven2 projects in such a structure is pretty stupid. :) However, so far doing something like this accidentially is a good way to lock yourself out of your project group...
well, I just took another look at this one and then it struck me. The way the sample is setup is after uncommenting the parent element in the parent-2 project, you basically get neverending loop of parents. Parent-1 has Parent-2 as parent which in turn has Parent-1 as parent. -> that's possibly something to deal with in maven itself (please file it a such) but not in the IDE integration. We just reuse maven codebase for project loading. resolving as later as the only way to fix the issue is to fix in maven and eventually upgrade to that version in netbeans
NetBeans.org Migration: changing resolution from LATER to WONTFIX