1 Reply Latest reply on Apr 5, 2017 10:55 AM by Anup Dey

    EAP 7 : Error during deployment

    A CY Newbie

      Hi dear developer,

       

      I have an error when i deploy my application with Jenkins  using the following command :

       

      jboss-cli-client.jar --connect --controller=***.***.***.***:9990 --user=******* --password=******* '--command=deploy --force target/************.war'

      I get the following stack trace :

      2017-03-23 09:47:35,533 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 84) WFLYUT0022: Unregistered web context: /Ans_Tucano_Services_Cms

      2017-03-23 09:47:35,535 INFO  [io.undertow.servlet] (ServerService Thread Pool -- 84) Destroying Spring FrameworkServlet 'dispatcherServlet'

      2017-03-23 09:47:35,552 INFO  [io.undertow.servlet] (ServerService Thread Pool -- 84) Closing Spring root WebApplicationContext

      2017-03-23 09:47:35,552 INFO  [org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext] (ServerService Thread Pool -- 84) Closing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@5feea56e: startup date [Thu Mar 23 09:45:12 UTC 2017]; root of context hierarchy

      2017-03-23 09:47:35,559 INFO  [org.springframework.context.support.DefaultLifecycleProcessor] (ServerService Thread Pool -- 84) Stopping beans in phase 2147483647

      2017-03-23 09:48:05,561 WARN  [org.springframework.context.support.DefaultLifecycleProcessor] (ServerService Thread Pool -- 84) Failed to shut down 1 bean with phase value 2147483647 within timeout of 30000: [org.springframework.jms.config.internalJmsListenerEndpointRegistry]

      2017-03-23 09:48:05,561 INFO  [org.springframework.context.support.DefaultLifecycleProcessor] (ServerService Thread Pool -- 84) Stopping beans in phase 0

      2017-03-23 09:48:05,564 INFO  [org.springframework.boot.actuate.endpoint.jmx.EndpointMBeanExporter] (ServerService Thread Pool -- 84) Unregistering JMX-exposed beans on shutdown

      2017-03-23 09:48:05,567 INFO  [org.springframework.boot.actuate.endpoint.jmx.EndpointMBeanExporter] (ServerService Thread Pool -- 84) Unregistering JMX-exposed beans

      2017-03-23 09:48:05,570 INFO  [org.springframework.jmx.export.annotation.AnnotationMBeanExporter] (ServerService Thread Pool -- 84) Unregistering JMX-exposed beans on shutdown

      2017-03-23 09:52:35,490 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: (undefined): java.lang.IllegalStateException: WFLYCTL0345: Timeout after 300 seconds waiting for existing service service jboss.deployment.unit."Ans_Tucano_Services_Cms.war".contents to be removed so a new instance can be installed.

        at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:2122)

        at org.jboss.as.server.deployment.ContentServitor.addService(ContentServitor.java:48)

        at org.jboss.as.server.deployment.DeploymentHandlerUtil.doDeploy(DeploymentHandlerUtil.java:161)

        at org.jboss.as.server.deployment.DeploymentHandlerUtil$4.execute(DeploymentHandlerUtil.java:269)

        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)

        at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)

        at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)

        at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344)

        at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)

        at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)

        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208)

        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130)

        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152)

        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148)

        at java.security.AccessController.doPrivileged(Native Method)

        at javax.security.auth.Subject.doAs(Subject.java:422)

        at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)

        at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148)

        at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)

        at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at java.lang.Thread.run(Thread.java:745)

        at org.jboss.threads.JBossThread.run(JBossThread.java:320)

       

       

      2017-03-23 09:57:35,495 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 3) WFLYCTL0349: Timeout after [300] seconds waiting for service container stability while finalizing an operation. Process must be restarted. Step that first updated the service container was 'full-replace-deployment' at address '[]'

      2017-03-23 09:57:35,511 INFO  [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0002: Content removed from location /usr/local/EAP-7.0.0/standalone/data/content/9f/88f72b86e0eb2504473c51fc71f70225aceecb/content

       

      Any idee about this error?

      I have been searching since several day,  but without success.

       

      Regards,

        • 1. Re: EAP 7 : Error during deployment
          Anup Dey Apprentice

          Is this a new deployment or an older application that just recently started exhibiting this issue? It may help to increase your jboss.as.management.blocking.timeout  (such as to 600/900 seconds).

           

          The timeout can be increased via the "jboss.as.management.blocking.timeout" system property.

           

          Try with setting "jboss.as.management.blocking.timeout" system property in configuration file i.e standalone-*.xml or domain.xml as per time required by your deployment to deploy like :

           

          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

          ...

          </extensions>

            <system-properties>

            <property name="jboss.as.management.blocking.timeout" value="..."/>  Here you can try with 600/900

            </system-properties>

          <management>

          ...

          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

           

            Use following CLI command to set it :

           

          For Standalone mode :

          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

          /system-property=jboss.as.management.blocking.timeout:add(value=....)  Here you can try with 600/900

          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

           

          If the issue continues to persist with the increased timeout, there may be some unexpected start up/deployment stall.