[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ] 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. -- This message was sent by Atlassian JIRA (v7.5.0#75005)