[jbosstools-issues] [JBoss JIRA] (JBIDE-11831) Remote server marked as stopped even if stopped failed

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697916#comment-12697916 ] 

Rob Stryker commented on JBIDE-11831:
-------------------------------------

> 2) Added a synchronous one-time poll before sending the remote stop command over the wire. This way if the server is already stopped, we'll find out. 

As #2 says, at the initiation of a stop() command, we do a one-time poll, before launching an appropriate poll thread, to just verify if the server is up or down once.  If the actual server is down, we simply set the server to stopped without sending any remote command. 
                
> Remote server marked as stopped even if stopped failed
> ------------------------------------------------------
>
>                 Key: JBIDE-11831
>                 URL: https://issues.jboss.org/browse/JBIDE-11831
>             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
>
>         Attachments: 305306.v3.patch, JBIDE-11831.patch
>
>
> Similarly to JBIDE-11825, when you stop a remote server and the shutdown command fails to stop the server process for some reason, the tooling will display the server as stopped even if in fact it is still running.
> It the status is Stopped, it should really be stopped.

--
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