3 Replies Latest reply on Jun 12, 2017 12:55 PM by ehugonnet

    Wildfly in Netbeans deployed twice

    gmalartre
    gmalartre Jun 9, 2017 3:18 PM

      Following previous discussion with Emmanuel Hugonnet. NetBeans is redeploying my maven ear a second time and I always have to wait 180s in between this redeployment to get a valid deploy.

        • 1. Re: Wildfly in Netbeans deployed twice
          ehugonnet
          ehugonnet Jun 12, 2017 3:24 AM (in response to gmalartre)

          I would say that the 180s period is the time it takes to redeploy the ear. That is one of the problem currently: we have to redeploy the full application to take the changes into account.

            • Actions
          • 2. Re: Wildfly in Netbeans deployed twice
            gmalartre
            gmalartre Jun 12, 2017 9:37 AM (in response to ehugonnet)

            If you refer to my previous pastebin link you will see that at line 1709. 14:25:11,119 we wait until 14:28:13,448 to move to the next line and that look like some sort of timeout of 180s (because I did not touch anything I just waited).

              • Actions
            • 3. Re: Wildfly in Netbeans deployed twice
              ehugonnet
              ehugonnet Jun 12, 2017 12:55 PM (in response to gmalartre)

              14:28:13,448 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment Takeda4473CRM-EAR-1.0-SNAPSHOT.ear (runtime-name: Takeda4473CRM-EAR-1.0-SNAPSHOT.ear) in 183125ms

              14:28:13,449 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "Takeda4473CRM-EAR-1.0-SNAPSHOT.ear" (runtime-name: "Takeda4473CRM-EAR-1.0-SNAPSHOT.ear")

              It takes 183 seconds to stop your application.

                • Actions