JBoss Boot error failed to start service jboss.web.deployment.default-host.

14:10:01,487 ERROR [Org.jboss.msc.service.fail] (MSC service thread 1-2) 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.4.GA-REDHAT-1.JAR:1.0.4.GA-REDHAT-1]

At Java.util.concurrent.threadpoolexecutor$worker.runtask (threadpoolexecutor.java:886) [rt.jar:1.6.0_25]

At Java.util.concurrent.threadpoolexecutor$worker.run (threadpoolexecutor.java:908) [rt.jar:1.6.0_25]

At Java.lang.Thread.run (thread.java:662) [rt.jar:1.6.0_25]

caused By:java.lang.IllegalArgumentException:JBWEB000250:Child container with name already exists

At Org.apache.catalina.core.ContainerBase.addChildInternal (containerbase.java:794)

At Org.apache.catalina.core.ContainerBase.addChild (containerbase.java:785)

At Org.apache.catalina.core.StandardHost.addChild (standardhost.java:353)

At Org.jboss.as.web.deployment.WebContextInjector.inject (webcontextinjector.java:62)

At Org.jboss.as.web.deployment.WebContextInjector.inject (webcontextinjector.java:38)

At Org.jboss.msc.inject.CastingInjector.inject (castinginjector.java:55) [jboss-msc-1.0.4.ga-redhat-1.jar:1.0.4. GA-REDHAT-1]

At Org.jboss.msc.service.ServiceControllerImpl.doInject (servicecontrollerimpl.java:1549) [ JBOSS-MSC-1.0.4.GA-REDHAT-1.JAR:1.0.4.GA-REDHAT-1]

At org.jboss.msc.service.servicecontrollerimpl.access$1900 (servicecontrollerimpl.java:49) [ JBOSS-MSC-1.0.4.GA-REDHAT-1.JAR:1.0.4.GA-REDHAT-1]

At Org.jboss.msc.service.servicecontrollerimpl$starttask.performinjections (servicecontrollerimpl.java:1780) [ JBOSS-MSC-1.0.4.GA-REDHAT-1.JAR:1.0.4.GA-REDHAT-1]

At Org.jboss.msc.service.servicecontrollerimpl$starttask.run (servicecontrollerimpl.java:1741) [ JBOSS-MSC-1.0.4.GA-REDHAT-1.JAR:1.0.4.GA-REDHAT-1]

... 3 more

Hey, should develop and test requirements, we test the environment The original war package name modified, the code package inside the configuration has also been modified, but after the deployment of a new war package, start error, check for half a day, the original is also to modify standalone.xml this configuration file. But I'm not using this configuration file here, look at the startup script

[Email protected] configuration]# cat/opt/jboss-eap-6.2/myrun_monitor.sh

Export Java_home= "/opt/jdk1.6.0_25"

Export java_opts= "-xms2048m-xmx2048m-xx:+useparallelgc-xx:maxpermsize=512m-djava.awt.headless=true

-dorg.jboss.resolver.warning=true-xx:+heapdumponoutofmemoryerror

-djava.security.egd=file:///dev/urandom.

-dsun.rmi.dgc.client.gcinterval=3600000

-dsun.rmi.dgc.server.gcinterval=3600000

-dsun.lang.classloader.allowarraysyntax=true "

rm-rf/opt/jboss-eap-6.2/monitor/tmp/*

rm-rf/opt/jboss-eap-6.2/monitor/data/*

Nohup bin/standalone.sh-djboss.server.base.dir=monitor-c=monitor.xml -dmonitor.port-offset=100- Dorg.jboss.as.logging.per-deployment=false-dfile.encoding=utf-8 >/dev/null 2>&1 &

Tailf Monitor/log/server.log

I am using this configuration file here, the path is

[Email protected] configuration]# pwd

/opt/jboss-eap-6.2/monitor/configuration

<subsystem xmlns= "urn:jboss:domain:web:1.5" default-virtual-server= "Default-host" native= "false" >

<connector name= "http" protocol= "http/1.1" scheme= "http" socket-binding= "http"/>

<virtual-server name= "Default-host" enable-welcome-root= "false" >

<alias name= "localhost"/>

<alias name= "example.com"/>

</virtual-server>

</subsystem>

This turns out to be true, instead of false, the original login authentication address is Http://10.224.173.206:8080/machine/machineHttpService

Now for Http://10.224.173.206:8180/#/pcList

This setting is to hide the war package, which is simple and easy to remember for login.

JBoss Boot error failed to start service jboss.web.deployment.default-host.