[
https://issues.jboss.org/browse/JBIDE-11990?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-11990:
---------------------------------------
I just tried now with jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar and
it behaves as I described - after reaching the time out the server is in
"Stopped" state, but the process keeps running on the server. Furthermore the
error after reaching the timeout is just empty, that is wrong :(
{code}
!ENTRY org.jboss.ide.eclipse.as.core 4 16842784 2012-05-28 12:43:07.244
!MESSAGE
{code}
When as7 server fails to start correctly but process is running it
fails to stop the process after reaching time out
--------------------------------------------------------------------------------------------------------------------
Key: JBIDE-11990
URL:
https://issues.jboss.org/browse/JBIDE-11990
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.CR1
Environment: JBT 3.3 nightly 2012-05-24
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.1
As a consequence of hitting JBIDE-11989 I found another problem. If for whatever reason
the server fails to start properly (e.g. -Djboss.bind.address.management set to null) this
is what happens:
1. The process keeps running on the remote host
2. The server is in Starting state until it reaches time out
3. This is where remote and local servers differ, but both behave wrongly
3.a - remote server: When time out is reached, server stops, but the process keeps
running - you have to kill it manually
3.b - local server: When time out is reached, server tries to stop, but fails doing so.
So you have to force stop and then it stops and the process is killed.
The the bigger problem is with remote servers - you have no way of stopping the server
other than sshing to the server and killing the process.
In the case of local server, it is not so bad, but still after the time out the tools
should be able to stop the server on first attempt.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira