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: - Add JBoss server minimal config instance - Start it using IDE - Try to stop it - RESULT: Stop will fail. It seems that user needs to shutdown the machine or to shutdown some java process in order to stop minimal config. Other standrard configurations such as default and all can't be started until the minimal is stopped. Compare with the following manual steps: - use "start.bat -c minimal" command to start server - use CTRL-C to stop it.
This Issue can't be fixed because of JBoss architecture. Minimal configuration can't be stopped "remotely" You can stop minimal configuration by Ctrl-C from console or by killing process. This issue must be added to release notes.
In this case appropriate message should be shown. I'll file appropriate issue.
Reopen according to zikmund comment for issue 60084 as follows: ------- Additional comments from zikmund Thu Jun 16 08:13:23 +0000 2005 ------- We should provide Stop action as a Kill of the process. See similar Tomcat issue 49543. It could avoid opening new console window.
We can't kill Jboss server process. Moreover Tomcat issue in New state and even not accepted, so you can't refer to it. Let it be RFE.
This is not just enhancement,it's serious bug,because we can't do something as basic as simply stop server,we just starte.I'm changing to DEFECT.
Main reason is: if user starts JBoss from NetBeans. He/she should be definitely able to stop it from NetBeans. Otherwise we will confuse users. I don't see any reason why do not kill process on Stop action. Kill could be silent without any warning to the user.
2 jpospisil: we can't stop minimal configuration because it impossible using standard stop script. 2 zikmund: what you mean by "kill process" indeed? I don't think that many users will use minimal configuration to work on it, so probably this issue not so important and can be moved to enhancements.
Then we should decrease priority (I'm OK with that), but it's still DEFFECT. Kill process: java.lang.Process.destroy();
Don't you think that it's not good solution to have possibility to stop server started from IDE and haven't for server started outside?
I think that it's a bad solution to allow user to start something and don't allow him to stop it.Something started outside IDE isn't important,it can be stopped also outside,but our case is acting inside the IDE,so it should be resolved also inside IDE. At least it's common behaviour the user expect from us,because Tomcat and SJS servers behave this way.
If we cannot stop the server it should at least fail immediately with an explanatory message. Then the user will know that the server has to be killed externally. I do not see why we would necessarilly need to provide the Stop action just because we provide the Start action. Stopping the server is not a primary use case and it clearly is not "something as simple as..". Starting the server, on the other hand, is very useful because you can just hit Run on project and it will start automatically. Killing the process could be done, but it only works for server started in IDE, so again you have an "inconsistency" which you fear so much ;-). IMO the Stop action failing with a good error message is better. Another option is to disable the minimal config. Decreasing to P3.
60083 is fixed. I am changing the issue to FEATURE just like Tomcat issue 49543. I do not plan to work on this in 4.2.
We already don't support a minimal configuration which would need a kill action.