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.
[20040215] Try to create a webmodule with /META-INF/context.xml outside of the IDE, mount it and execute. The deployment stuck somewhere in the middle of the deployment process (tomcat is started) and do not show any error message or an exception. The progress bar window remains opened forever. The problem is very likely caused by missing .nbattrs file in the META-INF directory.
Created attachment 13454 [details] Threaddump
Very strange. I (thought I) fixed 39937 on Feb 13 and the IDE should no longer store anything in nbattrs in META-INF and ignore it if present. Are you sure you see the nbattrs there for new module created in IDE? Are you sure you have 20040215? What makes you think this was the problem? I don't see anything related to (missing or invalid) configuration in td. Thanks.
I am really sorry Pavle to mislead you. I have dealt with the deployment today and realized that the source of the problem is somewhere else. I can reproduce the described problem by following this scenario: 1) run IDE with a brand-new userdir 2) mount a webmodule without any netbeans proprietary content like .nbattrs etc. 3) execute it 4) remove default server instance 5) add an external server instance 6) execute the wm again After the last step the external tomcat is started but the deployment stuck somewhere. The progress window show no message, there isn't any exception in the IDE output either. The user cannot execute the webmodule until s/he unmounts it (or shutdown the IDE), delete the .nbattrs from the root of the webmodule and mounts it again. Then the execution works well. I consider the described scenarion as not very often, but also not impossible. I am not sure what other parts of the functionality it can break so I'm leaving this bug as P2 until you investigate it. Thanks, Marek
Another simplier way how to reproduce it: 1) run the IDE with fresh userdir 2) convert sampledir to web and execute it 3) remove default server instance 4) add the instance back 5) execute the wm again
Can you still reproduce it? I tested both scenarios and it works for me.
I works fine now. I encountered another minor problem with the second deployment. When you follow the second scenario, after the second deployment 'java.lang.IllegalStateException: Context path /sampledir is already in use' exc. is printed into IDE output. The whole stack is attached.
Created attachment 13672 [details] java.lang.IllegalStateException: Context path /sampledir is already in use
verified the main problem