EAP 6 fails to start our deployment because of "IllegalArgumentException: Child container with name already exists"

Solution Verified - Updated -

Issue

  • JBoss fails to deploy our application with the following error:
ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.web.deployment.default-host./: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./: Failed to start service
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_34]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_34]
        at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_34]
Caused by: java.lang.IllegalArgumentException: Child container with name  already exists
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:805)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:793)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:356)
        at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)

Environment

  • JBoss Enterprise Application Platform (EAP) 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.