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

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-16588:
-------------------------------------

Well with the latest patches in master, exposing management port is the default for all as7 or later when in rse mode...   I know for as>7 we also used to terminate the remote process using a kill command, and I think I solved a bug today with rse host shells... see JBIDE-16634

I suggest you try this again once there's a new build on master [~mmalina].  It may very well be fixed :)   I'll give it another run through too. 
                
> 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