3 Replies Latest reply on Sep 6, 2013 2:23 AM by Yves Martin

    JBoss AS 7.1.0 domain mode deploy

    Fabiano Frizzo Newbie

      Hello Guys

       

      I'm trying to deploy an app.
      With JBoss started in domain mode.

       

      I am using the command.

       

      deploy /Volumes/Arquivos/app.war --all-server-groups

       

      But it is a long time, and does not deploy.

      Cancel the operation, with ctrl + c

      And get the following message on the terminal.

       

      Failed to add the deployment content to the repository: java.util.concurrent.ExecutionException: Operation failed

       

      Anyone have any ideas?

       

      I made no change in the settings of JBoss.

        • 1. Re: JBoss AS 7.1.0 domain mode deploy
          Yves Martin Newbie

          Got the same with a WAR and an other EAR (both larger than 100 Mb)

           

          jboss-cli is stuck here:

          "main" prio=10 tid=0x00007f21a4007800 nid=0x5288 in Object.wait() [0x00007f21a89ee000]
            java.lang.Thread.State: WAITING (on object monitor)
          at java.lang.Object.wait(Native Method)
          - waiting on (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
          at java.lang.Object.wait(Object.java:503)
          at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192)
          - locked (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
          at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266)
          - locked (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl)
          at org.jboss.as.controller.client.impl.AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get(AbstractModelControllerClient.java:363)
          at org.jboss.as.controller.client.impl.AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get(AbstractModelControllerClient.java:317)
          at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:137)
          at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:86)
          at org.jboss.as.cli.handlers.DeployHandler.execute(DeployHandler.java:568)
          at org.jboss.as.cli.handlers.DeployHandler.doHandle(DeployHandler.java:365)
          at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:84)
          at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:467)
          at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:478)
          at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1031)
          at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:208)
          at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:601)
          at org.jboss.modules.Module.run(Module.java:260)
          at org.jboss.modules.Main.main(Main.java:291)

          Even if host controller has reported:

           

          JBAS014900: Content added at location /opt/jboss/domain/data/content/f5/88b80e83b11449a016e695e638d0dfdc6b0d90/content
          

           

          Maybe it is fixed in 7.1.2 / EAP 6.1... to confirm

          • 2. Re: JBoss AS 7.1.0 domain mode deploy
            Tomaz Cerar Master

            Yes this was fixed in 7.1.2 and 7.2.

             

            i would recommend you to use 7.2/EAP 6.1.Alpha where this is fixed.

            • 3. Re: JBoss AS 7.1.0 domain mode deploy
              Yves Martin Newbie

              After a while, I decided to delete everything and get back to a clean JBoss, run my deployment script and it ends successfully then. Probably some internal state was messed up.