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

Rob Stryker (JIRA) jira-events at lists.jboss.org
Fri Jun 1 05:59:20 EDT 2012


     [ https://issues.jboss.org/browse/JBIDE-11831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBIDE-11831.
---------------------------------

    Resolution: Done


committed to cr1 and trunk.... changed pollthread.cancel() to add a null check. 
                
> 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, JBIDE-11831.v3.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

        


More information about the jbosstools-issues mailing list