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.
Created attachment 107671 [details] threaddump NetBeans 7.0 FCS Candidate (20110408) ------------------------ - created maven ee app, clean and build, tried to create session bean, ide froze. Thread dump attached. Please evaluate ASAP for potential stopper.
Should already be fixed in dev builds. Whether this is a 7.0 stopper is for someone else to decide, based on how reproducible the issue is. It is not a deadlock because the IDE should recover once indices are created, though this may take several minutes. I think the freeze will only happen if you have not yet indexed your Maven repositories, which would normally have already happened during daily use. The code in 7.0 is supposed to also be skipping repositories which are not yet indexed; perhaps some repo is marked as indexed but the index is out of date so an attempt to query it triggers a reindex? loadIndexingContext and getLoaded use slightly different logic to check if a repo is indexed, though it seems that presence in the "loaded" list should imply that loadIndexingContext would not call indexLoadedRepo, short of a race condition. (I think Tonda introduced getLoaded in bug #191313, so adding him to CC in case he has any insight on that.) *** This bug has been marked as a duplicate of bug 197510 ***
could you please check new threaddump2, if i am dealing with still the same thing? It seems like it happend to me again, yes, during indexing local repo, but was not freeze IMHO, since progress got stuck on 92% and IDE did not recover even after ~5 minutes. feel free to close again then.
Created attachment 107754 [details] threaddump2
FYI: Product Version: NetBeans IDE 7.0 (Build 201104080000) Java: 1.6.0_25; Java HotSpot(TM) 64-Bit Server VM 20.0-b11 System: Linux version 2.6.35-28-generic running on amd64; ANSI_X3.4-1968; en_US (nb) Userdir: /home/tomas/.netbeans/7.0
Yes, it is the same: "org.netbeans.modules.maven.execute.MavenCommandLineExecutor" daemon prio=10 tid=0x00007fd2fda08800 nid=0x1c23 in Object.wait() [0x00007fd2e5edb000] ... at org.netbeans.modules.maven.indexer.api.RepositoryQueries.findBySHA1(RepositoryQueries.java:209) at org.netbeans.modules.maven.classpath.EndorsedClassPathImpl.getResources(EndorsedClassPathImpl.java:113) ... (Regarding "freeze" vs. "deadlock": your thread dump shows the IDE in two active HTTP downloads; of course it is possible your network or the server was dead.) *** This bug has been marked as a duplicate of bug 197510 ***