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.
In Build 020130, if the user attempted to start a JSP or servlet debugging session while another debugger session was already active, an information dialog was given and the user was not allowed to start the new session. However, in Build 020201_1, no information dialog is given when the second start is attempted. The Tomcat server is restarted and the user will eventually hit a java.net.ConnectException (see attachment).
Created attachment 4541 [details] Exception which user will run into after second start is attempted.
forte EE 020202 strange, but the dialog is still there see an atachment
Created attachment 4554 [details] dialog
This bug is still reproduced with build 020318 under Solaris8 I have an exception: Tue Mar 19 14:48:28 GMT+03:00 2002: java.lang.Exception: tomcat is not stopped properly java.lang.Exception: tomcat is not stopped properly at org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.stopExecutio n(Tomcat40Installation.java:688) at org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.startServerI nDebugMode(Tomcat40Installation.java:518) at org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.synchronizeS tart(Tomcat40Installation.java:646) at org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.incrementalD eploy(Tomcat40Installation.java:402) at org.netbeans.modules.tomcat.tomcat40.Tomcat40Instance.deploy (Tomcat40Instance.java:262) at org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.doDeploy (DefaultServerInstanceManager.java:145) at org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.startDebug ger(DefaultServerInstanceManager.java:187) at org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.serverInst anceStartDebugging(DefaultServerInstanceManager.java:120) at org.netbeans.modules.j2ee.impl.DefaultExecPerformer.startDebugging (DefaultExecPerformer.java:127) at org.netbeans.modules.web.execution.WebDefaultExecPerformer.startDebugg ing(WebDefaultExecPerformer.java:242) at org.netbeans.modules.j2ee.impl.ServerDebuggerType.startDebugger (ServerDebuggerType.java:71) at org.netbeans.modules.j2ee.impl.ServerDebuggerType.startDebugger (ServerDebuggerType.java:63) at org.netbeans.modules.debugger.support.actions.StartAction.performActio n(StartAction.java:88) at org.openide.util.actions.NodeAction.performAction (NodeAction.java:180) at org.openide.util.actions.NodeAction.actionPerformed (NodeAction.java:171) at org.netbeans.core.ModuleActions$1.run (ModuleActions.java:105) at org.openide.util.Task.run(Task.java:152) [catch] at org.openide.util.RequestProcessor$ProcessorThread.run (RequestProcessor.java:622) But dialog "Start new session" is also shown. Exception shoudn't be throwned.
User was allowed to start second debugging session only on Solaris and Linux. Now it is protected on every OS.
Damian, what do you mean by words "Now it is protected on every OS." I still have an exception on Solaris 8. I don't think that bug is fixed if we still have an exception.
now you cannot start second JSP/servlet debugging session on every OS but I integrated it 3 hours ago, so you should have very fresh build, if you want to check it :)
and your exception is different to exception in this bug first exception is java.net.ConnectException but your exception is java.lang.Exception: tomcat is not stopped properly so you should file a new bug for your exception this bug is only about: you should not be able to start second JSP/servlet debugging session on every OS
New issue submitted 21716. I think it's related with this issue.
Changing target milestone to FFJ 4.0
Verified with S1S 5 build 030213_1.
Resolved for 3.4.x or earlier, no new info since then -> closing.