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 used: Netbean RC2 Plugin: 04/06 STEPS TO REPORDUCE: 1. Start Netbean IDE > AppServer 2. Create a web module 3. Create a JSP 4. Select Start Session > Run in Debugging 5. While waiting for the server to start in debuging mode toggle a break point and select step into BUG: Exception occurs in the ide.log file -------------------------------------------------------------------------------- Server deployer:Sun:AppServer::localhost:4848 stopped *********** Exception occurred ************ at Tue Apr 06 18:05:34 PDT 2004 javax.enterprise.deploy.spi.exceptions.TargetException: Unable to connect to admin-server. Please check if the server is up and running and that the hos t and port provided are correct. at com.sun.enterprise.deployapi.SunDeploymentManager.getAvailableModules(SunDeploymentManager.java:305) at com.sun.enterprise.tools.share.SunDeploymentManager.getAvailableModules(SunDeploymentManager.java:227) [catch] at org.netbeans.modules.j2ee.deployment.impl.TargetServer.getAvailableTMIDsMap(TargetServer.java:287) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.checkUndeployForSharedReferences(TargetServer.java:254) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.checkUndeployForSameReferences(TargetServer.java:204) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.processLastTargetModules(TargetServer.java:306) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.init(TargetServer.java:122) at org.netbeans.modules.j2ee.deployment.impl.TargetServer.startTargets(TargetServer.java:377) at org.netbeans.modules.j2ee.deployment.execution.ServerDebuggerType.doDeploy(ServerDebuggerType.java:225) at org.netbeans.modules.j2ee.deployment.execution.ServerDebuggerType.startDebugger(ServerDebuggerType.java:117) at org.netbeans.modules.j2ee.deployment.execution.ServerDebuggerType$1.run(ServerDebuggerType.java:105) at org.openide.util.Task.run(Task.java:136) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:686) Apr 6, 2004 6:05:35 PM com.sun.enterprise.deployapi.actions.DeployAction getVirtualServers SEVERE: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct. java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct. at com.sun.enterprise.admin.jmx.remote.comm.ServletConnection.handleException(ServletConnection.java:109) at com.sun.enterprise.admin.jmx.remote.comm.ServletConnection.send(ServletConnection.java:87) at com.sun.enterprise.admin.jmx.remote.comm.MBeanServerMessageConductor.invoke(MBeanServerMessageConductor.java:42) at com.sun.enterprise.admin.jmx.remote.internal.RemoteMBeanServerConnection.invoke(RemoteMBeanServerConnection.java:295) at com.sun.enterprise.deployapi.actions.DeployAction.getVirtualServers(DeployAction.java:183) at com.sun.enterprise.tools.studio.j2ee.incrdeploy.DirDeployAction.getProperties(DirDeployAction.java:204) at com.sun.enterprise.tools.studio.j2ee.incrdeploy.DirDeployAction.run(DirDeployAction.java:122) at java.lang.Thread.run(Thread.java:534) java.io.IOException: Unable to connect to admin-server. Please check if the server is up and running and that the host and port provided are correct. at com.sun.enterprise.admin.jmx.remote.comm.ServletConnection.handleException(ServletConnection.java:109) at com.sun.enterprise.admin.jmx.remote.comm.ServletConnection.send(ServletConnection.java:87) at com.sun.enterprise.admin.jmx.remote.comm.MBeanServerMessageConductor.invoke(MBeanServerMessageConductor.java:42) at com.sun.enterprise.admin.jmx.remote.internal.RemoteMBeanServerConnection.invoke(RemoteMBeanServerConnection.java:295) at com.sun.enterprise.deployapi.actions.DeployAction.getVirtualServers(DeployAction.java:183) at com.sun.enterprise.tools.studio.j2ee.incrdeploy.DirDeployAction.getProperties(DirDeployAction.java:204) at com.sun.enterprise.tools.studio.j2ee.incrdeploy.DirDeployAction.run(DirDeployAction.java:122) at java.lang.Thread.run(Thread.java:534)
Jim, I am asking you AGAIN: do not paste large blocks of text into issue comment, create and attachment. It is written in BOLD text on the bug submission page: You will have an opportunity to add attachments after this issue is created; please do not paste large amounts of text into the description. Thank you. This is not a showstopper for 3.6 will be solves in promoD. I assume the workaround is to wait for the server to come up. Reassigning to Martin to evaluate.
will look at what can be done here
The Step Into action is disabled during server startup phase.