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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-11831:
---------------------------------------------

comments for clarification:

Can singleUseShell now be null or is that just an extra guard added now ?

What happens if server can't be stopped - it stays in running state ? what if I stop the server manually, won't it return failure to stop and then still be in running state even though now it is for sure not running ?
                
> 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: 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