Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-1305

a file-scanner deployment that fails on boot will not be undeployed after failure

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 8.0.0.Beta1
    • None
    • None
    • None

    Description

      When an app is deployed via the deployments/ dir, but fails for some reason, it is marked as failed with a .failed marker and undeployed. When the AS is rebooted, it tries to redeploy the failure. If this deploy also fails, this new deployment isn't undeployed, and a .deployed marker is written to deployments.

      This is with the 7.2.0.Final used in Immutant, I've yet to try to build Immutant on top of 8.x.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2876 runtime-failure-causes-rollback does not seem to have effect when configured in model

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              chaowan@redhat.com Chao Wang
              tcrawley Toby Crawley (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: