ause:
In some situations if a deployment fails to deploy, the addition of the deployment content to the content repository will not be reverted.
Consequence:
Deployment content for flawed deployment archives can accumulate in the EAP content repository, wasting disk space.
Fix:
EAP now periodically runs a background process that checks for and removes content in the repository that is not referenced in the configuration model.
Result:
If an archive fails to deploy and it's content remains in the repository, the garbage collection protocol will remove it within 5 to 10 minutes.
DescriptionKenjiro Nakayama
2015-02-19 12:08:05 UTC
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.
EAP triggers :clean-obsolete-content() every 5 minutes. All unused content is marked as obsolete on first run, all marked stuff is removed on second run.
Verified on EAP 6.4.0.CR1
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.