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

After failed to deploy, remain deployment information in JBOSS_HOME/{standalone|domaine}/data/content directory

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • 1.0.0.Alpha19
    • Management
    • None

    Description

      Description of problem:
      ===
      
      - After failed to deploy, remain deployment information in JBOSS_HOME/{standalone|domaine}/data/content directory 
      - Please see following reproduce steps.
      
      How reproducible:
      ===
      
      Steps to Reproduce:
      1. Fail to deploy application via jboss-cli
      2. Find deployment info in JBOSS_HOME/{standalone|domaine}/data/content, but there are no standalone.xml in <deployments> tag.
      3. Fix deployment and success to deploy.
      4. Find "new" deployment info in JBOSS_HOME/{standalone|domaine}/data/content, and the old deployment info will be still there.
      
      - I know that as we changed application in step-3, its hash value was changed. And then, old info is remained in JBOSS_HOME/{standalone|domaine}/data/content. But I think it always happens and should be fixed.
      
      Actual results:
      
      - The deployment information which created when deploy was failed remains in JBOSS_HOME/{standalone|domaine}/data/content.
      
      Expected results:
      
      - The deployment information which created when deploy was failed should be removed if the deploy is failed.
      

      Attachments

        Issue Links

          Activity

            People

              chaowan@redhat.com Chao Wang
              chaowan@redhat.com Chao Wang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: