Invalid unmanaged deployment breaks working managed deployments in EAP 6

Environment

• Red Hat JBoss Enterprise Application Platform (EAP)
  • 6.4. CP4

Issue

• Invalid unmanaged deployment breaks working managed deployments in EAP 6.4
• While deploying applications with cli and the deployment directory in standalone mode. There is an unexpected behavior during development which can be reproduced the following way:
  • Deploy a working .war with cli (we do so with standard-deployments other applications rely on)
  • Stop Server
  • Copy a corrupt (e.g. a bad web.xml or jboss-web.xml) .war to the deployment directory of the standalone server
  • Start server
  • Result is Deployment from the first step has gone.

Resolution

Apply the latest cumulative patch to resolve it on EAP 6.4 and EAP 7.0

Root Cause

Invalid unmanaged deployment breaks working managed deployments - This content is not included.BZ1291710 / Content from issues.jboss.org is not included.JBEAP-4984

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.