Bug 1346552 - [GSS](6.4.z) If there are two deploy directories a deployment failure in one undeployes everything in the other
Summary: [GSS](6.4.z) If there are two deploy directories a deployment failure in one ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Microcontainer and Deployers
Version: 6.4.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.10
Assignee: Radovan Netuka
QA Contact: Peter Mackay
eap-docs
URL:
Whiteboard:
Depends On:
Blocks: eap6410-payload
TreeView+ depends on / blocked
 
Reported: 2016-06-15 02:11 UTC by Abhijit humbe
Modified: 2017-01-17 12:56 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 12:56:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Abhijit humbe 2016-06-15 02:11:51 UTC
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:

Comment 3 Radovan Netuka 2016-06-21 13:09:22 UTC
PR: https://github.com/jbossas/jboss-eap/pull/2799

Comment 4 Radovan Netuka 2016-06-21 13:10:15 UTC
Works well on EAP 7. No upstream is required.

Comment 7 Peter Mackay 2016-08-29 12:01:49 UTC
Verified with EAP 6.4.10.CP.CR2

Comment 8 Petr Penicka 2017-01-17 12:56:56 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.


Note You need to log in before you can comment on or make changes to this bug.