0 Replies Latest reply on Jul 2, 2013 3:39 AM by Milos Surducki

    jboss-as-maven-plugin deployment incomplete

    Milos Surducki Newbie

      I am trying to perform simple deployment of an ear file to standalone jboss 7 server using the plugin.

      The deployment appears to be OK


      [INFO] <<< jboss-as-maven-plugin:7.4.Final:deploy (default) @ tdi-bus-deploy <<<


      [INFO] --- jboss-as-maven-plugin:7.4.Final:deploy (default) @ tdi-bus-deploy ---

      02/07/2013 5:19:29 PM org.xnio.Xnio <clinit>

      INFO: XNIO Version 3.0.7.GA

      02/07/2013 5:19:29 PM org.xnio.nio.NioXnio <clinit>

      INFO: XNIO NIO Implementation Version 3.0.7.GA

      02/07/2013 5:19:30 PM org.jboss.remoting3.EndpointImpl <clinit>

      INFO: JBoss Remoting version 3.2.12.GA

      [INFO] ------------------------------------------------------------------------


      [INFO] ------------------------------------------------------------------------

      [INFO] Total time: 18.003s

      [INFO] Finished at: Tue Jul 02 17:19:32 EST 2013

      [INFO] Final Memory: 9M/25M

      [INFO] ------------------------------------------------------------------------


      The server log also acknowledges that the deplyment occured and ear file has made it to the server content directory under the generic name of "content".



      17:19:31,750 INFO  [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location C:\jboss-as-711\standalone\data\content\53\1f81b7964642ccacd3328ce47b37943f10f16a\content

      17:19:31,750 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "tdi-bus"

      17:19:31,984 INFO  [org.jboss.as.server] (management-handler-thread - 1) JBAS018559: Deployed "tdi-bus"



      The console also shows that the application is enabled however the deployment is incomplete.

      The servlets are not loaded and urls/endpoints are not available.


      Same ear file is succesfully deployed by dropping on to deployments directory, from the console or using jboss-cli.

      It looks as if the server can't properly activate the deployment from from the content directory.


      Any ideas ?