Bug 1291710 - [GSS](6.4.z) Invalid unmanaged deployment breaks working managed deployments
Summary: [GSS](6.4.z) Invalid unmanaged deployment breaks working managed deployments
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management, MSC
Version: 6.4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.9
Assignee: jboss-set
QA Contact: Martin Simka
URL:
Whiteboard:
Depends On:
Blocks: eap649-payload
TreeView+ depends on / blocked
 
Reported: 2015-12-15 13:34 UTC by Mustafa Musaji
Modified: 2019-11-14 07:14 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
broken war - invalid web.xml (2.18 KB, application/zip)
2015-12-15 13:34 UTC, Mustafa Musaji
no flags Details
client.war - working deployment (1.28 KB, application/zip)
2015-12-15 13:35 UTC, Mustafa Musaji
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-4984 0 Critical Verified (7.0.z) Invalid unmanaged deployment breaks working managed deployments 2017-09-19 06:27:33 UTC
Red Hat Issue Tracker WFCORE-64 0 Major Resolved Filesystem deployment scanner deployment failure removes unrelated deployments 2017-09-19 06:27:33 UTC
Red Hat Knowledge Base (Solution) 2416521 0 None None None 2016-06-29 05:47:57 UTC

Description Mustafa Musaji 2015-12-15 13:34:45 UTC
Created attachment 1106021 [details]
broken war - invalid web.xml

Description of problem:

Previously managed (CLI) deployed application is undeployed when you try and deploy a broken WAR

Version-Release number of selected component (if applicable):
EAP 6.4.4

How reproducible:
Everytime

Steps to Reproduce:
1) Start JBoss
2) Deploy valid client.war - file (see attachment) per CLI ('jboss-cli -c --commands="deploy client.war"')
3) Stop the JBoss
4) Put the invalid zclient.war - file (see attachment) in the deployments-folder
5) Start the JBoss again


Actual results:
Previous working deployment is unregistered

Expected results:
Previously working client.war shouldn't be unregistered


Additional info:
We know mixing CLI and unmanaged deployments for the same deployement is not recommended. We also know that mixing CLI and managed is not recommended BZ900548, but I don't think the previous working deployments should be undeployed.

Comment 1 Mustafa Musaji 2015-12-15 13:35:11 UTC
Created attachment 1106022 [details]
client.war - working deployment

Comment 2 Tomas Hofman 2016-01-07 14:42:39 UTC
PR: https://github.com/jbossas/jboss-eap/pull/2669

Comment 3 Mike McCune 2016-03-28 23:39:55 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Jiří Bílek 2016-06-22 07:18:20 UTC
Verified with EAP 6.4.9.CP.CR1

Comment 6 JBoss JIRA Server 2016-06-28 11:38:26 UTC
Tomas Hofman <thofman> updated the status of jira JBEAP-4984 to Resolved

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

Comment 8 Petr Penicka 2017-01-17 12:58:35 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.