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.
Steps to reproduce: 1. Mount web-module (from attachment). 2. Open test_jsp.jsp & jsp2.jsp 3. Start debugging test_jsp. 4. Execute jsp2.jsp 5. Start debugging jsp2.jsp Sometimes after step 5 I have exception, but if it's not occured, repeat again steps 3-5. Well reproduced under RH Linux 7.2 & Sparc Solaris 8 with Netbeans 3.4 RC2 (build 200208082340) P.S. May be this bug should be submitted to tomcatint component. If I'm not right, please correct me.
Created attachment 7073 [details] Web module
Created attachment 7074 [details] Localhost log (with exception inside)
Additional comments: Exception is showned inside localhost_log tab of output. Also, browser display exception instead of JSP.
Also I have following output to console: ========================================================= <sva@hercules(pts/32).321> ./runide.sh cannot load servlet name: jsp Internal HTTP server running on port 8082 IOManager.init Tab Closed org.netbeans.modules.debugger.jpda.JPDADebugger@cd67f IOManager.init Tab Closed org.netbeans.modules.debugger.jpda.JPDADebugger@510bb7 IOManager.init Tab Closed org.netbeans.modules.debugger.jpda.JPDADebugger@440d13 IOManager.init Tab Closed org.netbeans.modules.debugger.jpda.JPDADebugger@a867dc IOManager.init Tab Closed org.netbeans.modules.debugger.jpda.JPDADebugger@a30a0b IOManager.init Tab Closed org.netbeans.modules.debugger.jpda.JPDADebugger@6f9c62 Internal HTTP server stopped =========================================================
Better way to reproduce this bug is to press reload on browser, when starting new session of debugger or starting execution of JSP.
The exception that appears in the web browser that Vladimir sent to me privately (Vladimir, could you please attach this exception to this bug ?) shows that this bug is caused by bad synchronization inside Tomcat, as described in Tomcat bug 6907: http://issues.apache.org/bugzilla/show_bug.cgi?id=6907 This bug appears in all versions of Tomcat 4.0.x, and is fixed in 4.1.x. I suggest we mark this bug as "will not fix".
Created attachment 7089 [details] JPEG Picture with exception
Created attachment 7090 [details] Exception stack trace
Release note provided by Leslie: When testing or debugging web applications, an exception (org.apache.jasper.JasperException or javax.servlet.ServletException: duplicate class definition) may be thrown. It will appear in the server log file and/or in the web browser window. This bug is a consequence of Tomcat bug 6907, for details see http://issues.apache.org/bugzilla/show_bug.cgi?id=6907 . The workaround is to restart the Tomcat web server.
Fixed in Tomcat 5 -> fixed.
During verification of this issue I run into new issue. I was not able to debug any JSP in webmodule attached by Vladimir. I got exception in tomcat log. Tomcat was running, but didn't stop on breakpoint. I also tried to delete all .nbattrs files, web.ias, web.warContent, web.webj2eeri and web.webweblogic. Nothing helped. Debugging of other webmodules works.
Created attachment 13570 [details] Tomcat exception
Are you able to execute the JSP?
Yes, I can execute JSP. Tomcat also runs in debug mode, and debugger connets to it, but breakpoint isn't reached.
Right. Thanks. I was able to reproduce in the meantime, and I already know where's the problem. I'm working on it.
Fixed in trunk.
verified
will not relnote for 3.6; leaving keyword for benefit of 3.5-based releases