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.
1. register appserver in the ide 2. create a web project with tomcat as target 3. set a breakpoint in the index.jsp and call debug on the project -> debugger will stop at the breakpoint and tomcat server will get in the suspended state 4. call refresh on the appserver server instance node and you will get java.lang.RuntimeException: The Admin Server is stopped at a Break Point. No calls can be executed. Please note that this is not the only use case when this RE will occur. The way how the appserver plugin detects suspended state should be improved.
Created attachment 27249 [details] stack trace
is is new behaviour because of very changes in j2eeserver? What do you propose for improvement?
We tried hard to detect this state, and the conclusion was that if is much more complex that it appears. Not sure we can address this by 5.0. In anycase, it means that you cannot admin the AS server when the IDE is stopped at at break point (even if this is not on the AS process). Not really a big deal. Would you say it's a P4?
Jirka discovered this issue, so it should be more up to him to answer the P4 question ;) Jirka? No, it is not new behaviour. It was simply just not discovered before. Currently the isSuspended method checks only whether there is any active debug session with the host name the server is running on. This means that if there is any local server (e.g. Tomcat) in suspended state the local appserver will falsely think that it is suspended too, even if it's not running at all. The least we should do is to check also the debug port number, it is an easy fix and it will resolve the problem for the default configurations of Tomcat, JBoss and AppServer, since each of these servers uses different debug port number. If we would like to resolve this issue even better, the plugin would probably have to remember whether the server was started and the isSuspended method would have to check some isStarted flag. This would be, however, really a P4, I guess.
I agree it is a P4.
TM 5.0->TBD
this appears to be resolved
Verified.