[jbosstools-issues] [JBoss JIRA] (JBIDE-17050) A second running jboss server cannot be stopped

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-17050.
---------------------------------

    Resolution: Done


This has been committed. Basically, each launch controller can provide a matching shutdown controller if it wants, in the event a chosen shutdown controller (such as mgmt) doesn't know how to force-terminate. 

In this way, the mgmt shutdown controller can properly delegate the force-terminate to either the local or remote shutdowns. 
                
> A second running jboss server cannot be stopped
> -----------------------------------------------
>
>                 Key: JBIDE-17050
>                 URL: https://issues.jboss.org/browse/JBIDE-17050
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta1
>         Environment: JBDS 8.0.0.Beta1a B82
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.Beta2
>
>
> Today I set out to verify JBIDE-16480 - issues with detecting a server already running.
> You said that if you want to ensure detection of running instance between different server versions, you should use Web Poller. Well, I did that and ended up in a situation where I couldn't stop the second server at all.
> I know that you said previously that you can't cancel the action altogether once Start has been pressed. That would have been best. But we have to be able to then at least stop the server once it's been showed as started.
> Right now the only way to get out of this is eclipse restart.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira