Invalid unmanaged deployment breaks working managed deployments in EAP 6

Solution Verified - Updated -

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.

Environment

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

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content