Bug 1346552
| Summary: | [GSS](6.4.z) If there are two deploy directories a deployment failure in one undeployes everything in the other | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Abhijit humbe <abhumbe> |
| Component: | Microcontainer and Deployers | Assignee: | Radovan Netuka <rnetuka> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Peter Mackay <pmackay> |
| Severity: | unspecified | Docs Contact: | eap-docs <eap-docs> |
| Priority: | unspecified | ||
| Version: | 6.4.8 | CC: | ajustin, bmaxwell, dosoudil, fgavrilo, jtruhlar, pmackay, rnetuka |
| Target Milestone: | CR1 | ||
| Target Release: | EAP 6.4.10 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-17 12:56:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1339868 | ||
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. |
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: