[jbosstools-issues] [JBoss JIRA] (JBIDE-13959) AS7 custom deploy scanner should be removed upon server stop

[Martin Malina (JIRA)]

Martin Malina created JBIDE-13959:
-------------------------------------

             Summary: AS7 custom deploy scanner should be removed upon server stop
                 Key: JBIDE-13959
                 URL: https://issues.jboss.org/browse/JBIDE-13959
             Project: Tools (JBoss Tools)
          Issue Type: Feature Request
          Components: JBossAS/Servers
    Affects Versions: 4.1.0.Alpha2
            Reporter: Martin Malina
            Assignee: Rob Stryker
             Fix For: 4.1.0.Beta1


This is something that I noticed before but didn't care too much about.
But today it prevented me from starting a server, so I think it should be fixed if possible.
Today when I tried to start an EAP server I got this:
{code}

09:27:02,401 INFO  [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
09:27:05,636 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
09:27:05,948 INFO  [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
09:27:13,994 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([
    ("subsystem" => "deployment-scanner"),
    ("scanner" => "jbosstoolsscanner1")
]): java.lang.IllegalArgumentException: JBAS015053: /Users/rasp/jbossqa/JBDS/6.0.1/workspace-354/.metadata/.plugins/org.jboss.ide.eclipse.as.core/jboss-eap-6.0.1/deploy does not exist
	at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.<init>(FileSystemDeploymentService.java:165)
	at org.jboss.as.server.deployment.scanner.DeploymentScannerAdd.execute(DeploymentScannerAdd.java:118)
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
	at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:313) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_43]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_43]
	at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_43]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-2.jar:2.0.0.GA-redhat-2]

09:27:14,053 ERROR [org.jboss.as.controller.management-operation] JBAS014784: Failed executing subsystem deployment-scanner boot operations
09:27:14,060 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
09:27:14,117 INFO  [org.jboss.as] JBAS015950: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) stopped in 48ms
{code}

What's happening? It's simple, in another install of JBDS, in another workspace, I had this server and used workspace metadata deployment, so a custom deployment scanner was created. But since then I removed the server and workspace. But the deployment scanner still remained in the standalone.xml.

Would it be possible to remove it with server stop? Or do you see any other options here?

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