[
https://issues.jboss.org/browse/JBIDE-11825?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11825.
---------------------------------
Resolution: Done
There is no hard-and-fast way to recognize a completely failed start vs just a laggy
connection. The management poller has been fixed with some synchronization and other stuff
that wasn't working, and now a server which fails to start will be in
"Starting..." mode for 420 seconds. After that, it will stop on its own.
Users can force-stop it by right-clicking the server and selecting stop (do it 2x).
Remote server marked as started even if start failed
----------------------------------------------------
Key: JBIDE-11825
URL:
https://issues.jboss.org/browse/JBIDE-11825
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta3
Environment: JBT 3.3.0.Beta3 H152
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
When a remote AS7 fails to start (e.g. because of JBIDE-11824) and the process on the
remote server stops immediately AS tooling still marks it as Started in server view. I
think it is not acceptable to do that. Started should really mean started.
--
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