[ https://issues.jboss.org/browse/JBIDE-17473?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17473: ------------------------------------- That seems very strange. During force stop, the management shutdownc ontroller doesn't know how to force the termination, so it finds out how you launched it, and gets a shutdown controller that matches it. In this case, that'd be RSEJBossCommandLineShutdownController, a subclass of RSECommandLineShutdownController. RSECommandLineShutdownController has a forceStop() method which clearly resets the flag to false. See the last line here: {code} protected synchronized void forceStop() { if( getServer().getServerState() == IServer.STATE_STOPPED) return; String localPid = getProcessId(); ((ControllableServerBehavior)getControllableBehavior()).setServerStopped(); if( localPid != null ) { try { ServerShellModel model = RSEHostShellModel.getInstance().getModel(getServer()); String cmd = "kill -9 " + localPid; model.executeRemoteCommand("/", cmd, new String[]{}, new NullProgressMonitor(), 2000, true); } catch(CoreException ce ) { RSECorePlugin.pluginLog().logStatus(new Status(IStatus.ERROR, RSECorePlugin.PLUGIN_ID, "Unable to terminate remote process " + localPid, ce)); } } clearProcessId(); ((ControllableServerBehavior)getControllableBehavior()).putSharedData(IDeployableServerBehaviorProperties.NEXT_STOP_REQUIRES_FORCE, false); } {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)