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.
[beta candidate - 200509211930] -create ejb module -create new websvc -add operation to websvc - websvc's sources have to remain "dirty" -delete project with all sources -in Save dialog for modified classes press Save all => several error messages without any description & deadlock
Created attachment 25057 [details] thread dump
happens only if websvc impl bean and its SEI are opened in editor and both have "dirty" flag. Error message shows something like 'EJB???: ...no configuration node ""'
I experience similar behavior in all project types (without the deadlock though). Happens when deleting a project which has at least one modified file open in the editor.
> happens only if websvc impl bean and its SEI are opened in editor and both have > "dirty" flag. Error message shows something like 'EJB???: ...no configuration > node ""' It doesn't look like it's P1, neither Beta stopper ... I can't reproduce it with Java project. Could anybody reproduce it?
mmirilovic: Please try the following: 1. Create a new J2SE project. 2. Modify the created class, do not save it. 3. Try to delete the project (delete also sources). 4. After the confirmation dialog appears, do not press anything, only wait. 5. When the project is deleted, the project's node is still visible in the project's tab, sometimes a new project cannot be created, some exception(s) appear, etc. I did the following: 1. all files are unconditionally saved before any "delete-like" operation (project delete, move, rename). Not sure if this is correct. Filled issue #64932 for this. 2. the project close operation waits until the project is really closed (this was the main problem). I am pretty sure this cannot deadlock, as the thread that calls invokeAndWait is a thread that (AFAIK) does not hold any locks. Checking in projectuiapi/src/org/netbeans/modules/project/uiapi/DefaultProjectOperationsImplementation.java; /cvs/projects/projectuiapi/src/org/netbeans/modules/project/uiapi/DefaultProjectOperationsImplementation.java,v <-- DefaultProjectOperationsImplementation.java new revision: 1.14; previous revision: 1.13 done
jlahoda: Well, I can reproduce the project node stays visible in the Projects view, but there is no exception, and definitely none deadlock! Did you reproduce the deadlock? If so, it's beta stopper.
No, I was not able to reproduce the deadlock in either J2SE project or in the EJB module/project (as described in the original report).
I wasn't able to reproduce the deadlock either. To reporter: is the deadlock reproducible on your machine?
I am not able to reproduce this issue today. The fix should be integrated to beta branch but Honzo, please wait for verification from Jungi. Hi is going to take a look at it now.
in mentioned pre-beta build i was always able to reproduce the deadlock on my box, but in dev build 20050923-0044 i can not do so. Honzo, please, integrate the fix to the branch. thanks
Fixed also on the [release50_beta] branch. Please verify. Checking in projectuiapi/src/org/netbeans/modules/project/uiapi/DefaultProjectOperationsImplementation.java; /cvs/projects/projectuiapi/src/org/netbeans/modules/project/uiapi/DefaultProjectOperationsImplementation.java,v <-- DefaultProjectOperationsImplementation.java new revision: 1.13.2.1; previous revision: 1.13 done
Verified in 5.0 beta branch build #200509231930.