Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-2939

Disabled deployments in server group enabled after WAR is updated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0.Beta27
    • None
    • CLI
    • None

    • Centos 7
      OpenJDK

    • Hide

      Steps to reproduce:
      1. Deploy WAR file to domain controller
      2. Assign the WAR file to a server group, but disable it
      3. Update the contents of the WAR file via the CLI tool without listing any server groups i.e. deploy --force myApp.war
      4. Most of the time the deployment in the existing server group is enabled (it seems that very occasionally the deployment remains disabled)

      I would not expect that updating the file in the content repository would enable a disabled deployment in a server group. Maybe this is the expected behaviour though?

      Show
      Steps to reproduce: 1. Deploy WAR file to domain controller 2. Assign the WAR file to a server group, but disable it 3. Update the contents of the WAR file via the CLI tool without listing any server groups i.e. deploy --force myApp.war 4. Most of the time the deployment in the existing server group is enabled (it seems that very occasionally the deployment remains disabled) I would not expect that updating the file in the content repository would enable a disabled deployment in a server group. Maybe this is the expected behaviour though?
    • Compatibility/Configuration

      Updating the contents of a WAR file in a domain controller content repository will usually lead to a disabled deployment in a server group being enabled.

              ehugonne1@redhat.com Emmanuel Hugonnet
              mcasperson Matthew Casperson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: