A child container failed during start Tomcat boot Error _ exception

Source: Internet
Author: User
Serious: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException:Failed to start component [Standardengine[catalina]. Standardhost[localhost]. Standardcontext[/djadmin]] at Java.util.concurrent.FutureTask.report (futuretask.java:122) at java.util.concurrent. Futuretask.get (futuretask.java:192) at Org.apache.catalina.core.ContainerBase.startInternal (Containerbase.java : 939) at Org.apache.catalina.core.StandardHost.startInternal (standardhost.java:872) at Org.apache.catalina.util.Li Fecyclebase.start (lifecyclebase.java:150) at Org.apache.catalina.core.containerbase$startchild.call ( containerbase.java:1419) at Org.apache.catalina.core.containerbase$startchild.call (ContainerBase.java:1409) at JAV A.util.concurrent.futuretask.run (futuretask.java:266) at Java.util.concurrent.ThreadPoolExecutor.runWorker ( threadpoolexecutor.java:1142) at Java.util.concurrent.threadpoolexecutor$worker.run (ThreadPoolExecutor. java:617) at Java.lang.Thread.run (thread.java:745) caused by:org.apache.catalina.LifecycleException:Failed to start component [Standardengine[catalina]. Standardhost[localhost]. Standardcontext[/djadmin]] at Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:167) ... 6 more caused by:org.apache.catalina.LifecycleException:Failed to start component [ ORG.APACHE.CATALINA.WEBRESOURCES.STANDARDROOT@75A07D08] at Org.apache.catalina.util.LifecycleBase.start ( lifecyclebase.java:167) at Org.apache.catalina.core.StandardContext.resourcesStart (standardcontext.java:4860) at O Rg.apache.catalina.core.StandardContext.startInternal (standardcontext.java:4992) at Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150) ... 6 more caused By:org.apache.catalina.LifecycleException:Failed to initialize component [ ORG.APACHE.CATALINA.WEBRESOURCES.JARRESOURCESET@6400B8E4] at Org.apache.catalina.util.LifecycleBase.init (
   lifecyclebase.java:112) At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:140) at Org.apache.catalina.webresources.StandardRoot.startInternal (standardroot.java:709) at Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150) ... 9 caused By:java.lang.IllegalArgumentException:java.util.zip.ZipException:invalid LOC header (bad signature) a T Org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal ( abstractsinglearchiveresourceset.java:113) at Org.apache.catalina.util.LifecycleBase.init (lifecyclebase.java:107 )
    ...  caused By:java.util.zip.ZipException:invalid LOC header (bad signature) at Java.util.zip.ZipFile.read (Native Method in java.util.zip.zipfile.access$1400 (zipfile.java:60) at Java.util.zip.zipfile$zipfileinputstream.read (Zi pfile.java:717) at Java.util.zip.zipfile$zipfileinflaterinputstream.fill (zipfile.java:419) at Java.util.zip.Inflat Erinputstream.read (inflaterinputstream.java:158) at SuN.misc.ioutils.readfully (ioutils.java:65) at Java.util.jar.JarFile.getBytes (jarfile.java:425) at Java.util.jar.Jar File.getmanifestfromreference (jarfile.java:193) at Java.util.jar.JarFile.getManifest (jarfile.java:180) at Org.apac He.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal (Abstractsinglearchiveresourceset.java : 111) ... More June 28, 2017 4:33:38 pm org.apache.catalina.core.ContainerBase startinternal Serious: A child container failed during s Tart java.util.concurrent.ExecutionException:org.apache.catalina.LifecycleException:Failed to start component [ Standardengine[catalina]. Standardhost[localhost]] at Java.util.concurrent.FutureTask.report (futuretask.java:122) at Java.util.concurrent.Fu Turetask.get (futuretask.java:192) at Org.apache.catalina.core.ContainerBase.startInternal (containerbase.java:939 ) at Org.apache.catalina.core.StandardEngine.startInternal (standardengine.java:262) at Org.apache.catalina.util.Li Fecyclebase.stArt (lifecyclebase.java:150) at Org.apache.catalina.core.StandardService.startInternal (standardservice.java:422) A T Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150) at Org.apache.catalina.core.StandardServer.startInternal (standardserver.java:793) at Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150) at Org.apache.catalina.startup.Catalina.start (catalina.java:656) at Sun.reflect.NativeMethodAccessorImpl.invoke0 ( Native to Sun.reflect.NativeMethodAccessorImpl.invoke (nativemethodaccessorimpl.java:62) at Sun.reflect.Del Egatingmethodaccessorimpl.invoke (delegatingmethodaccessorimpl.java:43) at Java.lang.reflect.Method.invoke ( method.java:498) at Org.apache.catalina.startup.Bootstrap.start (bootstrap.java:355) at Org.apache.catalina.startup . Bootstrap.main (bootstrap.java:495) caused by:org.apache.catalina.LifecycleException:Failed to start component [ Standardengine[catalina]. Standardhost[localhost]] atOrg.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:167) at org.apache.catalina.core.containerbase$ Startchild.call (containerbase.java:1419) at Org.apache.catalina.core.containerbase$startchild.call ( containerbase.java:1409) at Java.util.concurrent.FutureTask.run (futuretask.java:266) at Java.util.concurrent.Threa Dpoolexecutor.runworker (threadpoolexecutor.java:1142) at Java.util.concurrent.threadpoolexecutor$worker.run ( threadpoolexecutor.java:617) at Java.lang.Thread.run (thread.java:745) caused by: Org.apache.catalina.lifecycleexception:a child container failed during start at Org.apache.catalina.core.ContainerBas E.startinternal (containerbase.java:947) at Org.apache.catalina.core.StandardHost.startInternal (Standardhost.java : 872) at Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150) ... 6 more June 28, 2017 4:33:38 pm Org.apache.catalina.startup.Catalina start serious: The required Server component failed to star t so Tomcat Is unable to start. org.apache.catalina.LifecycleException:Failed to start component [standardserver[8005]] at Org.apache.catalina.util. Lifecyclebase.start (lifecyclebase.java:167) at Org.apache.catalina.startup.Catalina.start (catalina.java:656) at Su N.reflect.nativemethodaccessorimpl.invoke0 (Native method) at Sun.reflect.NativeMethodAccessorImpl.invoke ( nativemethodaccessorimpl.java:62) at Sun.reflect.DelegatingMethodAccessorImpl.invoke ( delegatingmethodaccessorimpl.java:43) at Java.lang.reflect.Method.invoke (method.java:498) at ORG.APACHE.CATALINA.S Tartup. Bootstrap.start (bootstrap.java:355) at Org.apache.catalina.startup.Bootstrap.main (bootstrap.java:495) caused by: org.apache.catalina.LifecycleException:Failed to start component [Standardservice[catalina]] at Org.apache.catalina. Util. Lifecyclebase.start (lifecyclebase.java:167) at Org.apache.catalina.core.StandardServer.startInternal ( standardserver.java:793) at Org.apache.catalina.util.LifecyClebase.start (lifecyclebase.java:150) ... 7 more caused by:org.apache.catalina.LifecycleException:Failed to start component [Standardengine[catalina]] at org. Apache.catalina.util.LifecycleBase.start (lifecyclebase.java:167) at Org.apache.catalina.core.StandardService.startInternal (standardservice.java:422) at Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150) ... 9 more caused By:org.apache.catalina.lifecycleexception:a container failed during start at Org.apache.catalina . Core. Containerbase.startinternal (containerbase.java:947) at Org.apache.catalina.core.StandardEngine.startInternal ( standardengine.java:262) at Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150) ... One more June 28, 2017 4:33:38 pm Org.apache.coyote.AbstractProtocol pause Information: pausing Protocolhandler ["http-nio-8080"] June 28, 2017 4:33:38 pm Org.apache.coyote.AbstractProtocol pause Information: pausing Protocolhandler ["ajp-nio-8009"] June 28, 2017 4:33 :38 pm Org.apache.catalina.core.StandardService stopinternal Information: Stopping service Catalina June 28, 2017 4:33:38 pm Org.apach E.coyote.abstractprotocol destroy information: destroying Protocolhandler ["http-nio-8080"] June 28, 2017 4:33:38 pm Org.apache.coyo Te. Abstractprotocol destroy information: destroying Protocolhandler ["ajp-nio-8009"]

There are many reasons for this problem, recently encountered this problem, a search on the internet a variety of processing, tried a lot of species have not been resolved,
Encountered problems can not be urgent, the cause of this error is manifold, such as web.xml inside the configuration, some details on the
There is the reason for the caching of Tomcat and less packet or packet conflict.

This time I took the previous project to Re-import, and reported this mistake,
On the internet a lot of said is web.xml in the problem, I web.xml did not move at all,
One after the investigation found that the original is POI package import when the version inconsistency caused,

If you encounter such problems, it is impossible to see whether the server can be normal up, can not be the case is the server has problems, then you can change a clean server to try.
If the space is normal, create a new project to see if you can run, if you can, it is your project has problems, the project may be the problem of configuration problems, there can be a package of problems, and more stupid way is to the old project configuration slowly in the new project to try, can get a little past, Again to see if there have been errors, see where the problem, then the basic positioning is where the problem.

The WEB.XM and Pom files as well as the framework of the configuration file slowly test, this situation does not need to pass the Java file test,
It's going to be a big project.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.