Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-9101

AS7: Deployments should not be restarted for incremental deployments

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.3.0.M2
    • 3.3.0.M1
    • server
    • None
    • Hide
      1. make sure you have a project that is deployed to an as7 that you run (ex. create a Dynamic Web Project from scratch, add a index.html file to the WebContent folder)
      2. change a single file in your project (ex. index.html)

      Result:
      You see in the server log that the deployment is being restarted
      (ex. my project is called bogus and I catch the following in the server log when changing index.html:

      23:02:25,075 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "bogus.war"
23:02:25,298 INFO  [org.jboss.web] (MSC service thread 1-7) registering web context: /bogus

      Expected:
      The deployment should not get restarted. The file should get replaced by the new one and picked by AS7 instantly (without a restart of the deployment).

      Show
      make sure you have a project that is deployed to an as7 that you run (ex. create a Dynamic Web Project from scratch, add a index.html file to the WebContent folder) change a single file in your project (ex. index.html) Result: You see in the server log that the deployment is being restarted (ex. my project is called bogus and I catch the following in the server log when changing index.html: 23:02:25,075 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "bogus.war" 23:02:25,298 INFO [org.jboss.web] (MSC service thread 1-7) registering web context: /bogus Expected: The deployment should not get restarted. The file should get replaced by the new one and picked by AS7 instantly (without a restart of the deployment).

      Currently, if you have a project deployed to AS7 and change a single file, the deployment gets restarted (a new .dodeploy marker is created). This should not happen. Deployments should only be (re-)started (a .dodeploy marker created) in the following cases:

      1. new deployment
      2. cleaning
      3. full publish
      4. restarting

            rob.stryker Rob Stryker (Inactive)
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: