3 Replies Latest reply on Jul 2, 2013 7:44 AM by ctomc

    POST_MODULE deploy error

    thiagodonadel

      Hello.

       

      I'm having some problems with POST_MODULE deploy.

       

      I will show my structure in attached image.

       

      I have some .jars with ejbs, and have a WAR who acess those ejbs (my company don't want use a EAR file ... they want change a component without change everything)

      To use this structure I have this jboss-deployment-structure.xml on WAR project:

       

      <?xml version="1.0" encoding="UTF-8"?>

      <jboss-deployment-structure>

        <deployment>

          <dependencies>    

            <module name="deployment.core.jar" />

            <module name="deployment.global.jar" />

            <module name="deployment.sales.jar" />

            <module name="deployment.report.jar" />

            <module name="deployment.simulator.jar" />

          </dependencies>

        </deployment>

      </jboss-deployment-structure>

       

      But when I recompile one of those jars, and put in deployment folder I got this error:

       

      service jboss.deployment.unit."gesplan.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."gesplan.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "gesplan.war"

       

      And them the WAR project don't work anymore.

       

      Anyone knows how to solve this ??

       

      Thanks

       

      Thiago.

        • 1. Re: POST_MODULE deploy error
          sfcoy

          Hi there,

           

          What version of JBossAS/WildFly?

           

          Please attach a server.log containing the error that you're seeing.

           

          That aside, it looks to me like you're trying to build around a broken development process. The "want change a component without change everything" is an attitude out of the eighties/nineties that was a consequence of organisations not using repeatable build processes.

          • 2. Re: POST_MODULE deploy error
            thiagodonadel

            Hi Stephen!

             

            I'm using JBossAS 7.1.3 ...

             

            Here is the log:

             

            08:03:50,434 INFO  [org.jboss.as.osgi] (MSC service thread 1-6) JBAS011908: Unregister module: Module "deployment.report.jar:main" from Service Module Loader

            08:03:50,437 INFO  [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011908: Unregister module: Module "deployment.springteste.war:main" from Service Module Loader

            08:03:50,437 INFO  [org.jboss.as.osgi] (MSC service thread 1-5) JBAS011908: Unregister module: Module "deployment.gesplan.war:main" from Service Module Loader

            08:03:50,449 INFO  [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/springteste]] (MSC service thread 1-1) Destroying Spring FrameworkServlet 'springmvc'

            08:03:50,449 INFO  [org.springframework.web.context.support.XmlWebApplicationContext] (MSC service thread 1-1) Closing WebApplicationContext for namespace 'springmvc-servlet': startup date [Tue Jul 02 08:03:25 BRT 2013]; root of context hierarchy

            08:03:50,449 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016009: Stopping weld service for deployment report.jar

            08:03:50,456 INFO  [org.springframework.beans.factory.support.DefaultListableBeanFactory] (MSC service thread 1-1) Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@2baed605: defining beans [salesGridController,fabianoX,springTeste,fluxOne,flux,sessionInfoController,sessionInfoService,org.springframework.context.annotation.internalConfigurationAnnotationProcessor,org.springframework.context.annotation.internalAutowiredAnnotationProcessor,org.springframework.context.annotation.internalRequiredAnnotationProcessor,org.springframework.context.annotation.internalCommonAnnotationProcessor,org.springframework.web.servlet.resource.ResourceHttpRequestHandler#0,org.springframework.web.servlet.handler.SimpleUrlHandlerMapping#0,org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping,org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter,org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter,org.springframework.web.servlet.resource.ResourceHttpRequestHandler#1,org.springframework.web.servlet.handler.SimpleUrlHandlerMapping#1,mvcContentNegotiationManager,org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping#0,org.springframework.format.support.FormattingConversionServiceFactoryBean#0,org.springframework.validation.beanvalidation.LocalValidatorFactoryBean#0,org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter#0,org.springframework.web.servlet.handler.MappedInterceptor#0,org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver#0,org.springframework.web.servlet.mvc.annotation.ResponseStatusExceptionResolver#0,org.springframework.web.servlet.mvc.support.DefaultHandlerExceptionResolver#0,org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter#0,org.springframework.web.servlet.mvc.annotation.DefaultAnnotationHandlerMapping#0,viewResolver,org.springframework.context.annotation.CommonAnnotationBeanPostProcessor#0,org.springframework.context.annotation.ConfigurationClassPostProcessor.importAwareProcessor]; root of factory hierarchy

            08:03:50,478 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment report.jar in 45ms

            08:03:50,479 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "report.jar"

            08:03:50,496 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."gesplan.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."gesplan.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "gesplan.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.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]

                      at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]

            Caused by: java.lang.NullPointerException

                      at org.jboss.as.ee.component.deployers.ResourceInjectionAnnotationParsingProcessor.deploy(ResourceInjectionAnnotationParsingProcessor.java:138)

                      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

             

             

            08:03:50,497 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."springteste.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."springteste.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "springteste.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.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]

                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]

                      at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]

            Caused by: java.lang.NullPointerException

                      at org.jboss.as.ee.component.deployers.ResourceInjectionAnnotationParsingProcessor.deploy(ResourceInjectionAnnotationParsingProcessor.java:138)

                      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

             

             

            08:03:50,502 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment report.jar

            08:03:50,503 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ReportConfigurationService in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/ReportConfigurationService!br.com.gesplan.report.config.service.ReportConfigurationServiceRemote

                      java:app/report/ReportConfigurationService!br.com.gesplan.report.config.service.ReportConfigurationServiceRemote

                      java:module/ReportConfigurationService!br.com.gesplan.report.config.service.ReportConfigurationServiceRemote

                      java:jboss/exported/report/ReportConfigurationService!br.com.gesplan.report.config.service.ReportConfigurationServiceRemote

                      java:global/report/ReportConfigurationService

                      java:app/report/ReportConfigurationService

                      java:module/ReportConfigurationService

             

             

            08:03:50,503 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named PlanSceneryReportService in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/PlanSceneryReportService!br.com.gesplan.report.planning.sceneryreport.service.PlanSceneryReportServiceRemote

                      java:app/report/PlanSceneryReportService!br.com.gesplan.report.planning.sceneryreport.service.PlanSceneryReportServiceRemote

                      java:module/PlanSceneryReportService!br.com.gesplan.report.planning.sceneryreport.service.PlanSceneryReportServiceRemote

                      java:jboss/exported/report/PlanSceneryReportService!br.com.gesplan.report.planning.sceneryreport.service.PlanSceneryReportServiceRemote

                      java:global/report/PlanSceneryReportService

                      java:app/report/PlanSceneryReportService

                      java:module/PlanSceneryReportService

             

             

            08:03:50,503 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ReportService in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/ReportService!br.com.gesplan.report.main.service.ReportServiceRemote

                      java:app/report/ReportService!br.com.gesplan.report.main.service.ReportServiceRemote

                      java:module/ReportService!br.com.gesplan.report.main.service.ReportServiceRemote

                      java:jboss/exported/report/ReportService!br.com.gesplan.report.main.service.ReportServiceRemote

                      java:global/report/ReportService

                      java:app/report/ReportService

                      java:module/ReportService

             

             

            08:03:50,503 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named PlanReportService in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/PlanReportService!br.com.gesplan.report.planning.service.PlanReportServiceRemote

                      java:app/report/PlanReportService!br.com.gesplan.report.planning.service.PlanReportServiceRemote

                      java:module/PlanReportService!br.com.gesplan.report.planning.service.PlanReportServiceRemote

                      java:jboss/exported/report/PlanReportService!br.com.gesplan.report.planning.service.PlanReportServiceRemote

                      java:global/report/PlanReportService

                      java:app/report/PlanReportService

                      java:module/PlanReportService

             

             

            08:03:50,504 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ReportSecurityDAO in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/ReportSecurityDAO!br.com.gesplan.report.security.dao.ReportSecurityDAO

                      java:app/report/ReportSecurityDAO!br.com.gesplan.report.security.dao.ReportSecurityDAO

                      java:module/ReportSecurityDAO!br.com.gesplan.report.security.dao.ReportSecurityDAO

                      java:global/report/ReportSecurityDAO

                      java:app/report/ReportSecurityDAO

                      java:module/ReportSecurityDAO

             

             

            08:03:50,504 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named PlanReportDAO in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/PlanReportDAO!br.com.gesplan.report.planning.dao.PlanReportDAO

                      java:app/report/PlanReportDAO!br.com.gesplan.report.planning.dao.PlanReportDAO

                      java:module/PlanReportDAO!br.com.gesplan.report.planning.dao.PlanReportDAO

                      java:global/report/PlanReportDAO

                      java:app/report/PlanReportDAO

                      java:module/PlanReportDAO

             

             

            08:03:50,504 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ReportSecurityService in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/ReportSecurityService!br.com.gesplan.report.security.service.ReportSecurityServiceRemote

                      java:app/report/ReportSecurityService!br.com.gesplan.report.security.service.ReportSecurityServiceRemote

                      java:module/ReportSecurityService!br.com.gesplan.report.security.service.ReportSecurityServiceRemote

                      java:jboss/exported/report/ReportSecurityService!br.com.gesplan.report.security.service.ReportSecurityServiceRemote

                      java:global/report/ReportSecurityService

                      java:app/report/ReportSecurityService

                      java:module/ReportSecurityService

             

             

            08:03:50,504 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ReportConfigurationDAO in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/ReportConfigurationDAO!br.com.gesplan.report.config.dao.ReportConfigurationDAO

                      java:app/report/ReportConfigurationDAO!br.com.gesplan.report.config.dao.ReportConfigurationDAO

                      java:module/ReportConfigurationDAO!br.com.gesplan.report.config.dao.ReportConfigurationDAO

                      java:global/report/ReportConfigurationDAO

                      java:app/report/ReportConfigurationDAO

                      java:module/ReportConfigurationDAO

             

             

            08:03:50,504 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named PlanSceneryReportDatabaseLineDAO in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/PlanSceneryReportDatabaseLineDAO!br.com.gesplan.report.planning.sceneryreport.dao.PlanSceneryReportDatabaseLineDAO

                      java:app/report/PlanSceneryReportDatabaseLineDAO!br.com.gesplan.report.planning.sceneryreport.dao.PlanSceneryReportDatabaseLineDAO

                      java:module/PlanSceneryReportDatabaseLineDAO!br.com.gesplan.report.planning.sceneryreport.dao.PlanSceneryReportDatabaseLineDAO

                      java:global/report/PlanSceneryReportDatabaseLineDAO

                      java:app/report/PlanSceneryReportDatabaseLineDAO

                      java:module/PlanSceneryReportDatabaseLineDAO

             

             

            08:03:50,505 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ReportDAO in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/ReportDAO!br.com.gesplan.report.main.dao.ReportDAO

                      java:app/report/ReportDAO!br.com.gesplan.report.main.dao.ReportDAO

                      java:module/ReportDAO!br.com.gesplan.report.main.dao.ReportDAO

                      java:global/report/ReportDAO

                      java:app/report/ReportDAO

                      java:module/ReportDAO

             

             

            08:03:50,505 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named PlanReportLineDAO in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/PlanReportLineDAO!br.com.gesplan.report.planning.dao.PlanReportLineDAO

                      java:app/report/PlanReportLineDAO!br.com.gesplan.report.planning.dao.PlanReportLineDAO

                      java:module/PlanReportLineDAO!br.com.gesplan.report.planning.dao.PlanReportLineDAO

                      java:global/report/PlanReportLineDAO

                      java:app/report/PlanReportLineDAO

                      java:module/PlanReportLineDAO

             

             

            08:03:50,505 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named PlanSceneryReportHeaderDAO in deployment unit deployment "report.jar" are as follows:

             

             

                      java:global/report/PlanSceneryReportHeaderDAO!br.com.gesplan.report.planning.sceneryreport.dao.PlanSceneryReportHeaderDAO

                      java:app/report/PlanSceneryReportHeaderDAO!br.com.gesplan.report.planning.sceneryreport.dao.PlanSceneryReportHeaderDAO

                      java:module/PlanSceneryReportHeaderDAO!br.com.gesplan.report.planning.sceneryreport.dao.PlanSceneryReportHeaderDAO

                      java:global/report/PlanSceneryReportHeaderDAO

                      java:app/report/PlanSceneryReportHeaderDAO

                      java:module/PlanSceneryReportHeaderDAO

             

             

            08:03:50,560 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: report.jar

            08:03:50,570 INFO  [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.report.jar:main" from Service Module Loader

            08:03:50,582 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016008: Starting weld service for deployment report.jar

            08:03:50,740 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "report.jar" with deployment "report.jar"

            08:03:50,741 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report

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

                  service jboss.deployment.unit."gesplan.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."gesplan.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "gesplan.war"

            • 3. Re: POST_MODULE deploy error
              ctomc

              Deployment dependancies ware added in 7.2 and they don't work in 7.1.x

               

              Can you try with 7.2.0.Final (EAP6.1.Alpha)  or with WildFly 8 alpha2?