Description of problem: When jboss is configured to have two deploy directories, if a war file fails to deploy in one of them everything in the other deploy directory is undeployed in addition to the war file that failed to deploy. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Configure two deployment directories <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/> <deployment-scanner name="new-scanner" path="new_deployment_dir" relative-to="jboss.server.base.dir" scan-interval="5000"/> </subsystem> 2. Pleace valid application in "deployments" directory and invalid application in "new_deployment_dir" and start server. 3. check log file we can see application from "deployments" directory is undeployed. Actual results: Expected results: Additional info:
PR: https://github.com/jbossas/jboss-eap/pull/2799
Works well on EAP 7. No upstream is required.
Verified with EAP 6.4.10.CP.CR2
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.