[jbosstools-issues] [JBoss JIRA] (JBIDE-14024) war deployed to remote as7/eap6 is undeployed immediately

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-14024:
---------------------------------------

I just tried again and I noticed this thing:
After the server startup, a deployment scanner is added:
{code}
09:47:30,674 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) started in 5235ms - Started 136 of 217 services (80 services are passive or on-demand)
09:47:38,877 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/rasp/jbossqa/runtimes/jboss-eap-6.0.1/standalone/deployments
{code}

This is wrong, because it is a duplicate of the default scanner. See this in the standalone.xml:
{code}

            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000""
/>
            <deployment-scanner name="jbosstoolsscanner1" path="/home/rasp/jbossqa/runtimes/jboss-eap-6.0.11
/standalone/deployments/" scan-interval="5000"/>
{code}

And once I deploy a war, this happens:
{code}
09:50:09,166 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
09:50:10,413 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
09:50:10,437 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "dynproj.war"
09:50:10,852 INFO  [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register module: Module "deployment.dynproj.war:main" from Service Module Loader
09:50:11,059 INFO  [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: /dynproj
09:50:11,187 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dynproj.war"
09:50:16,205 INFO  [org.jboss.as.osgi] (MSC service thread 1-2) JBAS011908: Unregister module: Module "deployment.dynproj.war:main" from Service Module Loader
09:50:16,243 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment dynproj.war in 43ms
09:50:16,354 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "dynproj.war"
09:50:21,356 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}

The main problem is the two deployment scanners I believe - they compete between them and it is kind of unpredictable who wins.
                
> war deployed to remote as7/eap6 is undeployed immediately
> ---------------------------------------------------------
>
>                 Key: JBIDE-14024
>                 URL: https://issues.jboss.org/browse/JBIDE-14024
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.1.0.Alpha2
>         Environment: JBDS 7.0.0.Alpha2 B135
> EAP 6.1.0.ER4 / EAP 6.0.1 / AS 7.1.1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>            Priority: Blocker
>              Labels: respin-b
>             Fix For: 4.1.0.Beta1
>
>
> When I set up a remote EAP 6.1 with the management port enabled and then try to deploy a dynamic web project (exploded war), it gets deployed, but then undeployed right afterwards.
> This is in the remote server log:
> {code}
> 12:00:39,808 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
> 12:00:43,746 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
> 12:00:43,750 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "dynproj.war" (runtime-name: "dynproj.war")
> 12:00:43,811 INFO  [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018210: Register web context: /dynproj
> 12:00:43,923 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dynproj.war" (runtime-name : "dynproj.war")
> 12:00:48,932 INFO  [org.jboss.web] (ServerService Thread Pool -- 58) JBAS018224: Unregister web context: /dynproj
> 12:00:48,951 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment dynproj.war (runtime-name: dynproj.war) in 22ms
> 12:00:49,041 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "dynproj.war" (runtime-name: "dynproj.war")
> 12:00:54,043 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
> {code}

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