[jbosstools-issues] [JBoss JIRA] (JBIDE-16588) Remote EAP 6.2 fails to stop

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-16588:
---------------------------------------

I'm not 100% sure, but I think this worked in the past - even if management port was not set up, the tools would shutdown the server using the shutdown script.
If that's not possible anymore and the only way to make EAP6/AS7/WF work remotely is by setting up management, then this would require some changes in the UI - it would have to be the default and only option - why give users an option that will never work.
                
> Remote EAP 6.2 fails to stop
> ----------------------------
>
>                 Key: JBIDE-16588
>                 URL: https://issues.jboss.org/browse/JBIDE-16588
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Alpha2
>         Environment: JBDS 8.0.0.Alpha2a B70
> EAP 6.2.0.GA
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 4.2.0.Beta1
>
>         Attachments: remote-server-stop-error.png
>
>
> When I create a remote EAP 6.2 server (ssh connection) without using the management port, the server starts and deploys ok, but when I try to stop it, I get this error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-02-14 16:44:14.239
> !MESSAGE Server JBoss EAP 6.2 Server marvin failed to stop.
> {code}
> Very informative ;)
> !remote-server-stop-error.png!
> The server remains "Started" and the java process on the remote machine is still running. If I try it again and again, the result is the same. So the only way of stopping the server is killing the java process on the remote machine. But Eclipse will still show Started, so need a 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