[jbosstools-issues] [JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-26311:
-------------------------------------

So I found I was doing some things differently. 

1) I was not downloading the runtime, but using a local one.
2) I was not using my IP address, but rather the ssh host named "localhost"

I did not expect 1) would change anything. I thought maybe fixing 2) would cause me to replicate it. 

Unfortunately I still cannot replicate. Would you be able to trace through this? You'll want to set a breakpoint in RSEJBossCommandLineShutdownController.stopImpl(etc).  You'll also want to trace into the superclass calls, especially the eventual call to gracefulStop(). 

The gracefulStop() method should be trying to execute a command like as follows:

/home/rob/apps/jboss/unzipped/jboss-eap-7.1.0.zip.expanded/bin/jboss-cli.sh --connect command=:shutdown

As for the exceptions in your log, I've discovered their cause. While your server is configured to use command-line / filesystem operations only, and not management, we never converted our deployment scanner utility to have a command-line implementation. The server adapter is still trying to customize the deployment scanners via management, but mgmt is not exposed. 




> EAP 7.1 fails to stop when connected over ssh
> ---------------------------------------------
>
>                 Key: JBIDE-26311
>                 URL: https://issues.jboss.org/browse/JBIDE-26311
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.9.0.AM2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>              Labels: regression
>         Attachments: JBIDE-26311.local.ogv
>
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)