Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-14303

CLONE - war deployed to remote as7/eap6 is undeployed immediately

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.1.0.Alpha2
    • 4.1.0.Alpha2
    • server
    • Hide

      1. Create a remote as7/eap6 server with management port enabled
      2. Start the server and make sure it is up and connected
      3. Deploy a simple dynamic web project
      4. Watch the remote server log and see what happens
      5. The app ends up undeployed - FAIL

      Show
      1. Create a remote as7/eap6 server with management port enabled 2. Start the server and make sure it is up and connected 3. Deploy a simple dynamic web project 4. Watch the remote server log and see what happens 5. The app ends up undeployed - FAIL
    • Hide

      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

      Show
      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

      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:

      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

              manderse@redhat.com Max Andersen
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: