[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:all-tabpanel ]

Martin Malina updated JBIDE-14024:
----------------------------------

    Workaround Description: 
There are a couple of workarounds:
a) Do not check enable the management port when setting up the remote server
b) Remove the duplicate deployment server from the remote server's standalone.xml once the server has been started
c) Use a custom deployment directory - this way the added deployment scanner will point somewhere else than the default one and they will not collide

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