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

[Rob Stryker (JIRA)]

Rob Stryker created JBIDE-16900:
-----------------------------------

             Summary: Remote EAP 6.2 fails to stop - null argument
                 Key: JBIDE-16900
                 URL: https://issues.jboss.org/browse/JBIDE-16900
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: server
    Affects Versions: 4.2.0.Beta1
         Environment: JBDS 8.0.0.Beta1 B78
            Reporter: Rob Stryker
            Assignee: Rob Stryker
            Priority: Blocker
             Fix For: 4.2.0.Beta1


I cannot stop a remote server. It's EAP 6.2 without a runtime and with management operations enabled.

When I click stop, I get this error:
!null-argument.png!

And this is in the workspace log:
{code}
!ENTRY org.eclipse.core.jobs 4 2 2014-03-26 11:39:00.141
!MESSAGE An internal error occurred during: "Stopping JBoss EAP 6.2 marvin".
!STACK 0
org.eclipse.core.runtime.AssertionFailedException: null argument:
	at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
	at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
	at org.jboss.ide.eclipse.as.core.util.RemotePath.initialize(RemotePath.java:642)
	at org.jboss.ide.eclipse.as.core.util.RemotePath.<init>(RemotePath.java:197)
	at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleNestedDeployPath(ModuleDeploymentPrefsUtil.java:159)
	at org.jboss.tools.as.core.internal.modules.ModuleDeploymentPrefsUtil.getModuleTreeDestinationFullPath(ModuleDeploymentPrefsUtil.java:65)
	at org.jboss.tools.as.core.server.controllable.subsystems.internal.ModuleDeployPathController.getDeployDirectory(ModuleDeployPathController.java:110)
	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServer.getDeploymentLocation(DeployableServer.java:254)
	at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.getDeployLocationFolders(AbstractDeploymentScannerAdditions.java:161)
	at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:76)
	at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75)
	at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58)
	at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
	at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:242)
	at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3670)
	at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3627)
	at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
{code}

There is no way to stop the server - you can try as many times as you like to click Stop, but each time you get the error and the server is still started.

--
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