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.
Created attachment 1106022 [details] client.war - working deployment
PR: https://github.com/jbossas/jboss-eap/pull/2669
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Verified with EAP 6.4.9.CP.CR1
Tomas Hofman <thofman> updated the status of jira JBEAP-4984 to Resolved
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.