[
https://issues.jboss.org/browse/JBIDE-12123?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-12123:
---------------------------------------
Now it works as expected (I guess). When you stop the server but it fails to stop (as
described in JBIDE-11831) you will get an error soon. And the server will remain Started.
So the only way to stop is to kill the process on the server and then click Stop again.
Verified in JBDS 6.0.0.Beta1 B25. Will close when testing 3.3.2.
When remote server fails to stop process is not terminated even if
user opts for that
-------------------------------------------------------------------------------------
Key: JBIDE-12123
URL:
https://issues.jboss.org/browse/JBIDE-12123
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.2, 4.0.0.Beta1
With JBIDE-11831 the situation with stopping remote servers is now improved, but it's
still not ideal.
If the shutdown command fails we display an error: Server XX failed to stop. If you try
again, it does the same. If you try for the third time, it will keep stopping until the
timeout is reached and then a message is displayed: Server ... is not responding. Would
you like to terminate the server or keep waiting?
I hit terminate and nothing happens.
Also, this message is accompanied by an empty error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira