Eclipse Maven Project error 2 of a child container failed during start

Problem: I took an eclipse Maven project with my colleague and imported an error, mainly showing a child container failed during start

Specific errors are as follows

June 02, 2018 12:08:50pm Org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING: [Setpropertiesrule]{server/service/engine/host/context} Setting ' source ' to ' org.eclipse.jst.jee.server:UcomWechat 'Did not find a matching property. June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log information: Server version:apache Tomcat/9.0.0. M17 June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log information: Server Built:jan10 2017 20:59:20UTC June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log information: Server number:9.0.0.0June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log info: OS name:windows10June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log information: OS Version:10.0June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log info: architecture:amd64 June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log info: Java home:d:\program files\java\jdk1.8. 0_121\jre June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log information: JVM Version:1.8.0_121-B13 June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log information: JVM vendor:oracle Corporation June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log Info: catalina_base:d:\workspace\.metadata\.plugins\or G.ECLIPSE.WST.SERVER.CORE\TMP1 June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log info: Catalina_home:d:\tomcat9.0June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log message: Command line argument:-dcatalina.base=D:\WORKSPACE\.METADATA\.PLUGINS\ORG.ECLIPSE.WST.SERVER.CORE\TMP1 June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log message: Command line argument:-dcatalina.home=d:\tomcat 9.0June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log message: Command line argument:-dwtp.deploy=D:\workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp1\wtpwebapps June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log message: Command line argument:-djava.endorsed.dirs=d:\tomcat 9.0\endorsed June02, 2018 12:08:50pm Org.apache.catalina.startup.VersionLoggerListener Log message: Command line argument:-dfile.encoding=GBK June02, 2018 12:08:50pm Org.apache.catalina.core.AprLifecycleListener lifecycleevent Info: The APR based Apache Tomcat Native Library which a Llows optimal performance in production environments is not found on the Java.library.path:d:\program files\java\jdk1.
    8.0_121\bin; C:\WINDOWS\Sun\Java\bin; C:\WINDOWS\system32; C:\WINDOWS; C:\ProgramData\Oracle\Java\javapath; C:\Windows\system32; C:\Windows; C:\Windows\System32\Wbem; C:\Windows\System32\WindowsPowerShell\v1.0\; C:\Program Files (x86) \nvidia Corporation\physx\common; C:\WINDOWS\system32; C:\WINDOWS; C:\WINDOWS\System32\Wbem; C:\WINDOWS\System32\WindowsPowerShell\v1.0\;D: \python\python36\scripts\;D: \python\python36\;%userprofile%\appdata\local\microsoft\windowsapps;; C:\Program Files (x86) \ssh Communications security\ssh Secure Shell;. June02, 2018 12:08:50pm Org.apache.coyote.AbstractProtocol init info: Initializing Protocolhandler ["Http-nio-80"] June02, 2018 12:08:50pm Org.apache.tomcat.util.net.NioSelectorPool getsharedselector Info: Using a shared selector forServlet write/Read June02, 2018 12:08:50pm Org.apache.coyote.AbstractProtocol init info: Initializing Protocolhandler ["Ajp-nio-8009"] June02, 2018 12:08:50pm Org.apache.tomcat.util.net.NioSelectorPool getsharedselector Info: Using a shared selector forServlet write/Read June02, 2018 12:08:50pm Org.apache.catalina.startup.Catalina Load Info: initialization processed in998Ms June02, 2018 12:08:50pm Org.apache.catalina.core.StandardService startinternal Info: Starting service Catalina June02, 2018 12:08:50afternoon Org.apache.catalina.core.StandardEngine startinternal info: Starting Servlet engine:apache Tomcat/9.0.0. M17 June02, 2018 12:08:51afternoon Org.apache.catalina.core.ContainerBase startinternal Grave: A child container failed during Startjava.util.concurrent.ExecutionException:org.apache.catalina.LifecycleException:Failed to initialize component [[email protected]] 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.LifecycleBase.start (Lifecyclebase.java:183) 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.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 initialize component [[e-mail protected]] at Org.apach E.catalina.util.lifecyclebase.handlesubclassexception (Lifecyclebase.java:441) at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:139) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:173) at Org.apache.catalina.webresources.StandardRoot.startInternal (Standardroot.java:708) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:183) at Org.apache.catalina.core.StandardContext.resourcesStart (Standardcontext.java:4832) at Org.apache.catalina.core.StandardContext.startInternal (Standardcontext.java:4964)    ... 7morecaused by:java.lang.IllegalArgumentException:java.util.zip.ZipException:invalid LOC header (bad signature) At Org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal ( Abstractsinglearchiveresourceset.java:113) at Org.apache.catalina.util.LifecycleBase.init (Lifecyclebase.java:136)    ... 12morecaused by:java.util.zip.ZipException:invalid LOC header (bad signature) at Java.util.zip.ZipFile.read (Native Method) at java.util.zip.zipfile.access$1400 (zipfile.java:60) at Java.util.zip.zipfile$zipfileinputstream.read (Zipfile.java:717) at Java.util.zip.zipfile$zipfileinflaterinputstream.fill (Zipfile.java:419) at Java.util.zip.InflaterInputStream.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.JarFile.getManifestFromReference (Jarfile.java:193) at Java.util.jar.JarFile.getManifest (Jarfile.java:180) at Org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal ( Abstractsinglearchiveresourceset.java:111)    ... 13More June02, 2018 12:08:51afternoon Org.apache.catalina.core.ContainerBase startinternal Grave: A child container failed during Startjava.util.concurrent.executionexception:org.apache.catalina.lifecycleexception:a Child container failed During start 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.StandardEngine.startInternal (Standardengine.java:262) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:183) at Org.apache.catalina.core.StandardService.startInternal (Standardservice.java:422) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:183) at Org.apache.catalina.core.StandardServer.startInternal (Standardserver.java:793) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:183) at Org.apache.catalina.startup.Catalina.start (Catalina.java:655) at Sun.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.startup.Bootstrap.start (Bootstrap.java:355) at Org.apache.catalina.startup.Bootstrap.main (Bootstrap.java:495) caused By:org.apache.catalina.lifecycleexception:a child container failed during start at org.apache.catalina.co Re. Containerbase.startinternal (Containerbase.java:948) at Org.apache.catalina.core.StandardHost.startInternal (Standardhost.java:872) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:183) 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.ThreadPoolExecutor.runWorker (Threadpoolexecutor.java:1142) at Java.util.concurrent.threadpoolexecutor$worker.run (Threadpoolexecutor.java:617) at Java.lang.Thread.run (Thread.java:745) June02, 2018 12:08:51pm Org.apache.catalina.startup.Catalina Start Critical: The required Server component failed to start so Tomcat are unable to Start.org.apache.catalina.lifecycleexception:a child container failed during start at Org.apache.catalina.core.Contai Nerbase.startinternal (Containerbase.java:948) at Org.apache.catalina.core.StandardEngine.startInternal (Standardengine.java:262) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:183) at Org.apache.catalina.core.StandardService.startInternal (Standardservice.java:422) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:183) at Org.apache.catalina.core.StandardServer.startInternal (Standardserver.java:793) at Org.apache.catalina.util.LifecycleBase.start (Lifecyclebase.java:183) at Org.apache.catalina.startup.Catalina.start (Catalina.java:655) at Sun.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.startup.Bootstrap.start (Bootstrap.java:355) at Org.apache.catalina.startup.Bootstrap.main (Bootstrap.java:495) June02, 2018 12:08:51pm Org.apache.coyote.AbstractProtocol Pause Info: pausing Protocolhandler ["Http-nio-80"] June02, 2018 12:08:51pm Org.apache.coyote.AbstractProtocol Pause Info: pausing Protocolhandler ["Ajp-nio-8009"] June02, 2018 12:08:51pm Org.apache.catalina.core.StandardService stopinternal info: Stopping service Catalina June02, 2018 12:08:51pm Org.apache.coyote.AbstractProtocol Destroy info: destroying Protocolhandler ["Http-nio-80"] June02, 2018 12:08:51pm Org.apache.coyote.AbstractProtocol Destroy info: destroying Protocolhandler ["Ajp-nio-8009"]

View Code

Eclipse errors such as

This error is almost fatal, many colleagues have met, then the solution of what? A lot of people have removed the Tomcat server and then re-add to solve, but I am here to continue to operate this step does not work, also some people say that the MAVEN package conflict or Maven dependency is not added caused, so my solution is as follows

1: Because the suspicion is the Maven warehouse problem, so I re-download maven and configure the environment variables, configure the PATH variable

Http://mirror.bit.edu.cn/apache/maven/maven-3/3.5.3/binaries/apache-maven-3.5.3-bin.zip

Test maven at the command line to make sure the MAVEN environment is OK

2: Reconfigure the MAVEN environment for Eclipse

First, create a new D:\maven\repository folder as the local repository, default to the C drive under my users, here to create a new directory for easy to find

Next modify D:\apache-maven-3.5.3-bin\conf We extracted from the website of Maven directory configuration directory settings.xml, such as

Then go to eclipse to set up, as we enter the new MAVEN profile address, the system will automatically identify our new local warehouse location, click Apply, click OK

After configuring OK in the previous step, we right-click on the Item-maven-update project, force update is mandatory update

This time the tool will download the required jar to the local repository according to Pom.xml from the public repository, as shown in the download complete

To complete the configuration here, we clean the project, and then remove the server to re-create a server based on Tomcat9, right-click to run the discovery error no longer occurs

Eclipse Maven Project error 2 of a child container failed during start