3 Replies Latest reply on May 19, 2014 12:35 AM by lalitshaktawat

    Cannot deploy war project [Failed to process phase POST_MODULE...]

    markjasonn

      Hi.

       

      First time here in the forum. I hope someone can help me with this.

       

      I cannot deploy my war project using JBoss 7.1.3 Server. I keep getting this error below:

       

      17:59:11,235 INFO  [org.jboss.modules] JBoss Modules version 1.1.3.GA

      17:59:11,337 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      17:59:11,381 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.3.Final "Arges" starting

      17:59:12,053 INFO  [org.jboss.as.server.deployment.scanner] JBAS015003: Found myproject.war in deployment directory. To trigger deployment create a file called myproject.war.dodeploy

      17:59:12,065 INFO  [org.xnio] XNIO Version 3.0.6.GA

      17:59:12,067 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      17:59:12,070 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.6.GA

      17:59:12,075 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.8.SP1

      17:59:12,089 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

      17:59:12,098 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

      17:59:12,111 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      17:59:12,115 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)

      17:59:12,127 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem

      17:59:12,132 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

      17:59:12,134 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem

      17:59:12,138 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

      17:59:12,146 INFO  [org.jboss.as.security] (MSC service thread 1-8) JBAS013170: Current PicketBox version=4.0.13.Final

      17:59:12,148 INFO  [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service

      17:59:12,150 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      17:59:12,152 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]

      17:59:12,263 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.12.Final)

      17:59:12,318 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.5.GA

      17:59:12,507 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-localhost/127.0.0.1:8080

      17:59:12,542 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "myproject-ds.xml"

      17:59:12,543 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "myproject.war"

      17:59:12,544 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory D:\JStudio\jboss-as-7.1.3.Final\standalone\deployments

      17:59:12,548 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447

      17:59:12,549 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999

      17:59:12,739 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      17:59:12,754 INFO  [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011907: Register module: Module "deployment.myproject-ds.xml:main" from Service Module Loader

      17:59:12,759 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [eca_caseDatasource]

      17:59:12,759 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [myprojectDatasource]

      17:59:18,875 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_cs.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,875 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_de_DE.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,875 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_es.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,876 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_fr.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,876 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_hu.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,876 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_it.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,876 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_ja_JP.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_ko_KR.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_pl.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_pt_BR.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_ru.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,877 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_zh_CN.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,878 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry derbyLocale_zh_TW.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,895 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry iText-toolbox.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/itext.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,895 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry iText-toolbox-2.1.2.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/itext.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,895 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry bcmail-jdk14-138.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/itext.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,896 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry bcprov-jdk14-138.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/itext.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,901 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jaxp-api.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/saaj-api.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,901 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jax-qname.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/saaj-api.jar  does not point to a valid jar for a Class-Path reference.

      17:59:18,901 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry servlet.jar in /D:/JStudio/jboss-as-7.1.3.Final/standalone/deployments/myproject.war/WEB-INF/lib/saaj-api.jar  does not point to a valid jar for a Class-Path reference.

      17:59:19,051 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'

      17:59:19,051 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'

      17:59:19,061 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for myproject

      17:59:19,061 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for eca_case

      17:59:19,235 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment "deployment.myproject.war" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.

      17:59:19,235 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-6) JBAS018567: Deployment "deployment.myproject.war" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.

      17:59:19,466 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named EjbSynchronizations in deployment unit deployment "myproject.war" are as follows:

       

          java:global/myproject/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations

          java:app/myproject/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations

          java:module/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations

          java:global/myproject/EjbSynchronizations

          java:app/myproject/EjbSynchronizations

          java:module/EjbSynchronizations

       

      17:59:19,466 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named TimerServiceDispatcher in deployment unit deployment "myproject.war" are as follows:

       

          java:global/myproject/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher

          java:app/myproject/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher

          java:module/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher

          java:global/myproject/TimerServiceDispatcher

          java:app/myproject/TimerServiceDispatcher

          java:module/TimerServiceDispatcher

       

      17:59:19,469 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."myproject.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."myproject.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "myproject.war"

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_27]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_27]

          at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_27]

      Caused by: java.lang.NullPointerException

          at org.jboss.as.jpa.processor.PersistenceRefProcessor.getPersistenceUnitBindingSource(PersistenceRefProcessor.java:202)

          at org.jboss.as.jpa.processor.PersistenceRefProcessor.getPersistenceUnitRefs(PersistenceRefProcessor.java:123)

          at org.jboss.as.jpa.processor.PersistenceRefProcessor.processDescriptorEntries(PersistenceRefProcessor.java:74)

          at org.jboss.as.ee.component.deployers.AbstractDeploymentDescriptorBindingsProcessor.deploy(AbstractDeploymentDescriptorBindingsProcessor.java:100)

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]

          ... 5 more

       

      17:59:19,476 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "myproject.war"

      17:59:19,476 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "myproject-ds.xml"

      17:59:19,477 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

      JBAS014777:   Services which failed to start:      service jboss.deployment.unit."myproject.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."myproject.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "myproject.war"

       

        • 1. Re: Cannot deploy war project [Failed to process phase POST_MODULE...]
          lalitshaktawat

          Hi Jason

           

          By viewing of standalone.xml not able to find out your war deployment method. There are several way to deploy your project in JBoss AS. Short method is simple. Put your war file inside JBOSS_HOME/standalone/deployments folder. If you are not using this method. So you can try this.

          2. Other one is also simple but for other method you have to specified path of you war file in standalone.xml file as well as you have to create module.xml for path.

          3. Using management console (GUI) it will work on JBoss AS on running state.

          4. Using management CLI : Using command line interface.

           

          So make sure about path.

           

          Try with 1st method. Let me know about if any issue.

           

          Lalit

          • 2. Re: Cannot deploy war project [Failed to process phase POST_MODULE...]
            markjasonn

            Hi Lalit

             

            Thanks for your prompt reply!

            I forgot to say that I am using ant to deploy my project. And upon checking, everytime I explode my project, it creates the war on JBOSS_HOME/standalone/deployments folder.

            Does this mean that there is something wrong the war that was built??

            • 3. Re: Cannot deploy war project [Failed to process phase POST_MODULE...]
              lalitshaktawat

              Hi Jason

               

              Ant support maven repository. Ant and maven used for apache-tomcat and support HTTP-1.0 protocol. JBoss is also supporting both. I am not sure about your project. Ant and maven inbuilt package come with some JBoss AS flavor. So check in your machine.

              If you are having war files. You can directly deploy your project by using of first method.

               

              try and let me know.

               

              Thanks