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 6.1 (Build 200807020101) VM: Java HotSpot(TM) Client VM, 1.5.0_15-b04, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_15-b04 OS: SunOS, 5.10, x86 User Comments: I had some nb module projects open in the IDE. I updated my IDE. The modules do not appear in the projects window.
Created attachment 63852 [details] stacktrace
Did it happen just once? After the restart when IDE was updated? Or is it constant problem? What did you updated? Thanks for more info.
I have worked around this issue. here is what I did to work-around the issue. I looked in the logs and saw some other exceptions about 'class not found' from the SQE plugin. I uninstalled those plugins. I reinstalled the SQE plugins Now, things are much happier.
*** Issue 139298 has been marked as a duplicate of this issue. ***
*** Issue 139503 has been marked as a duplicate of this issue. ***
Build: NetBeans IDE 6.1 (Build 200804211638) VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06 OS: SunOS, 5.11, x86 User Comments:
Created attachment 64544 [details] stacktrace
Build: NetBeans IDE 6.1 (Build 200804211638) VM: Java HotSpot(TM) Client VM, 10.0-b22, Java(TM) SE Runtime Environment, 1.6.0_06-b02 OS: Windows XP, 5.1, x86 User Comments:
Created attachment 64697 [details] stacktrace
This issue has already 10 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=71746
Looks like some kind of race condition. J2SESources tries to register the J2SEProject as an owner of the external root but does not verify that the J2SEProject's constructor has actually completed first. However the use of postWriteRequest is supposed to make this task run after the whole write-access block including ABPFS.loadProject has completed. I guess that Mutex trickery is not working for some reason. Possible solution: give up on helper2Project and make getProjectFor just be a convenience method to call PM.findProject on the project directory specified by the helper. But I don't know what affect that would have on the stack trace displayed here, which shows gPF being called within the dynamic scope of findProject; would it result in a recursive call to findProject on the same dir?
Last report is from 6.1, problem probably vanished with other changes.