运行Maven项目时出现invalid LOC header (bad signature)错误,Tomcat不能正常启动
作为Maven小白,今天这问题困扰了我好久,经过多次在网上查询,终于找到了原因。明明一个小问题却耗费很多时间,着实不应该,所以必须记录一下。
报错信息如下:
对话框:
控制台:
- <span style="font-size:14px;"><span style="color:#ff0000;">严重: A child container failed during start
- java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/SpringMvcController]]
- at java.util.concurrent.FutureTask.report(Unknown Source)
- at java.util.concurrent.FutureTask.get(Unknown Source)
- at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
- at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
- at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
- at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
- at java.util.concurrent.FutureTask.run(Unknown Source)
- at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
- at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
- at java.lang.Thread.run(Unknown Source)
- Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/SpringMvcController]]
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
- ... 6 more
- Caused by: org.apache.catalina.LifecycleException: Failed to start component [org.apache.catalina.webresources.StandardRoot@43cd5898]
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
- at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4909)
- at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5039)
- 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@4d31c0af]
- at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
- at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:699)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
- ... 9 more
- Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: invalid LOC header (bad signature)
- at org.apache.catalina.webresources.JarResourceSet.initInternal(JarResourceSet.java:96)
- at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
- ... 12 more
- Caused 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(Unknown Source)
- at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source)
- at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(Unknown Source)
- at java.util.zip.InflaterInputStream.read(Unknown Source)
- at sun.misc.IOUtils.readFully(Unknown Source)
- at java.util.jar.JarFile.getBytes(Unknown Source)
- at java.util.jar.JarFile.getManifestFromReference(Unknown Source)
- at java.util.jar.JarFile.getManifest(Unknown Source)
- at org.apache.catalina.webresources.JarResourceSet.initInternal(JarResourceSet.java:94)
- ... 13 more
- 十一月 29, 2016 2:54:19 下午 org.apache.catalina.core.ContainerBase startInternal
- 严重: A child container failed during start
- java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]
- at java.util.concurrent.FutureTask.report(Unknown Source)
- at java.util.concurrent.FutureTask.get(Unknown Source)
- at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
- at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
- at org.apache.catalina.core.StandardService.startInternal(StandardService.java:439)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
- at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:769)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
- at org.apache.catalina.startup.Catalina.start(Catalina.java:625)
- at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
- at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
- at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
- at java.lang.reflect.Method.invoke(Unknown Source)
- at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
- at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)
- Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
- at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
- at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
- at java.util.concurrent.FutureTask.run(Unknown Source)
- at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
- at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
- at java.lang.Thread.run(Unknown Source)
- Caused by: org.apache.catalina.LifecycleException: A child container failed during start
- at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:924)
- at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
- ... 6 more
- 十一月 29, 2016 2:54:19 下午 org.apache.catalina.startup.Catalina start
- 严重: The required Server component failed to start 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:154)
- at org.apache.catalina.startup.Catalina.start(Catalina.java:625)
- at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
- at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
- at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
- at java.lang.reflect.Method.invoke(Unknown Source)
- at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
- at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)
- Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardService[Catalina]]
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
- at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:769)
- 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:154)
- at org.apache.catalina.core.StandardService.startInternal(StandardService.java:439)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
- ... 9 more
- Caused by: org.apache.catalina.LifecycleException: A child container failed during start
- at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:924)
- at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
- at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
- ... 11 more
- 十一月 29, 2016 2:54:19 下午 org.apache.coyote.AbstractProtocol pause
- 信息: Pausing ProtocolHandler ["http-nio-8080"]
- 十一月 29, 2016 2:54:19 下午 org.apache.coyote.AbstractProtocol pause
- 信息: Pausing ProtocolHandler ["ajp-nio-8009"]
- 十一月 29, 2016 2:54:19 下午 org.apache.catalina.core.StandardService stopInternal
- 信息: Stopping service Catalina
- 十一月 29, 2016 2:54:19 下午 org.apache.coyote.AbstractProtocol destroy
- 信息: Destroying ProtocolHandler ["http-nio-8080"]
- 十一月 29, 2016 2:54:19 下午 org.apache.coyote.AbstractProtocol destroy
- 严重: Failed to destroy end point associated with ProtocolHandler ["http-nio-8080"]
- java.lang.NullPointerException
- at org.apache.tomcat.util.net.NioEndpoint.releaseCaches(NioEndpoint.java:305)
- at org.apache.tomcat.util.net.NioEndpoint.unbind(NioEndpoint.java:481)
- at org.apache.tomcat.util.net.AbstractEndpoint.destroy(AbstractEndpoint.java:823)
- at org.apache.coyote.AbstractProtocol.destroy(AbstractProtocol.java:533)
- at org.apache.catalina.connector.Connector.destroyInternal(Connector.java:1023)
- at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:305)
- at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:588)
- at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:305)
- at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:859)
- at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:305)
- at org.apache.catalina.startup.Catalina.start(Catalina.java:629)
- at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
- at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
- at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
- at java.lang.reflect.Method.invoke(Unknown Source)
- at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
- at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)
- 十一月 29, 2016 2:54:19 下午 org.apache.coyote.AbstractProtocol destroy
- 信息: Destroying ProtocolHandler ["ajp-nio-8009"]
- 十一月 29, 2016 2:54:19 下午 org.apache.coyote.AbstractProtocol destroy
- 严重: Failed to destroy end point associated with ProtocolHandler ["ajp-nio-8009"]
- java.lang.NullPointerException
- at org.apache.tomcat.util.net.NioEndpoint.releaseCaches(NioEndpoint.java:305)
- at org.apache.tomcat.util.net.NioEndpoint.unbind(NioEndpoint.java:481)
- at org.apache.tomcat.util.net.AbstractEndpoint.destroy(AbstractEndpoint.java:823)
- at org.apache.coyote.AbstractProtocol.destroy(AbstractProtocol.java:533)
- at org.apache.catalina.connector.Connector.destroyInternal(Connector.java:1023)
- at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:305)
- at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:588)
- at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:305)
- at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:859)
- at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:305)
- at org.apache.catalina.startup.Catalina.start(Catalina.java:629)
- at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
- at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
- at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
- at java.lang.reflect.Method.invoke(Unknown Source)
- at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
- at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)</span>
- </span>
原因:
提取错误的关键信息
说明Jar包出现了问题。
那么接下来就要找哪个jar包出现了问题:
方法1、可通过右击项目名 -> Run as -> Maven test ,这时控制台会报哪个jar包出错。 (也可以打开DOS命令窗口,切换至项目目录,运行mvn test命令,和Eclipse的控制台输出信息一致)
方法2、如果方法1未出现任何错误信息,那么就使用笨办法。打开项目中的pom.xml文件,在自己的Maven本地仓库去查找pom.xml文件中每一个dependency节点所对应的jar包版本。一个一个对比,看看是否都正常下载。
这里,我找到了本地仓库中出现的jar包错误:
解决方法:
既然jar包未下载成功,那么重新下载就行了。如果重新下载还是不能成功,那就在网上下载同版本的拷贝进去。
删除掉该jar包所在目录下的所有文件后,重新运行maven install。
这时,可看到jar包已正常下载。
再次运行项目,右击项目 -> Run as -> Run on server 。可以发现,项目能正常运行了。
运行Maven项目时出现invalid LOC header (bad signature)错误,Tomcat不能正常启动的更多相关文章
- 运行Maven项目时出现invalid LOC header (bad signature)
为Maven小白,今天这问题困扰了我好久,经过多次在网上查询,终于找到了原因.明明一个小问题却耗费很多时间,着实不应该,所以必须记录一下. 报错信息如下: 对话框: 控制台: <span s ...
- [转]maven编译时出现读取XXX时出错invalid LOC header (bad signature)
maven编译时出现读取XXX时出错invalid LOC header (bad signature) 一.发现问题右击pom.xml,run as —> maven install,会看到c ...
- maven编译时出现读取XXX时出错invalid LOC header (bad signature)
问题原因 该包没有下载正确. 解决办法 找到该包的目录,删除该包重新下载即可. 重新下载后用maven test一下,红叉消失.
- 解决Maven打包提示:读取C:\Users\Administrator\.m2\repository\ch\qos\logback\logback-classic\1.2.3\logback-classic-1.2.3.jar时出错; invalid LOC header (bad signature)
1.打包情况 虽然提示读取jar包出错,但是还是能打包成功,在执行打的jar包时会报错,说找不到相关的类. 2.解决方案 从提示的路径可以找到对应的jar包,但为什么会读取错误呢?尝试着双击打开log ...
- Maven错误:XXX时出错; invalid LOC header (bad signature)的解决方法
错误原因是该包没下载成功,比如网络问题等因素. 解决方法:进入本地仓库删除该包,然后再执行打包或部署等操作即可.
- groovy-2.4.11.jar时出错; invalid LOC header (bad signature)
Information:java: Errors occurred while compiling module 'security'Information:javac 1.8.0_131 was u ...
- maven 错误:读取 xxx.jar 时出错;invalid LOC header (bad signature) 1 错误
reqHeader:{Accept=text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8, Upgrade-Insecure- ...
- maven提示invalid LOC header (bad signature)的解决办法
今天执行mvn test的时候提示: 错误:读取 /home/subaochen/.m2/repository/org/slf4j/slf4j-api/1.6.1/slf4j-api-1.6.1.ja ...
- maven下载的jar文件出现invalid LOC header (bad signature)
有的时候maven下载了相对应的jar文件,但是某些类无法被引入,在eclipse打开该jar文件,发现相对应的类是invalid LOC header (bad signature),这时把mave ...
随机推荐
- Jenkins系统监测
Jenkins 是一个开源项目,提供了一种易于使用的持续集成系统,使开发者从繁杂的集成中解脱出来,专注于更为重要的业务逻辑实现上.同时 Jenkins 能实施监控集成中存在的错误,提供详细的日志文件和 ...
- Vue 学习笔记之快速入门篇
Vue (读音 /vjuː/,类似于 view) 是一套用于构建用户界面的渐进式框架.与其它大型框架不同的是,Vue 被设计为可以自底向上逐层应用.Vue 的核心库只关注视图层,不仅易于上手,还便于与 ...
- Python:decorator [转]
Python中的装饰器是你进入Python大门的一道坎,不管你跨不跨过去它都在那里. 为什么需要装饰器 我们假设你的程序实现了say_hello()和say_goodbye()两个函数. def sa ...
- March 05th, 2018 Week 10th Monday
Fortune favors the bold. 勇者天佑. It has been increasingly apparent that courage is the main quality we ...
- Spring缓存注解@Cacheable、@CacheEvict、@CachePut使用
从3.1开始,Spring引入了对Cache的支持.其使用方法和原理都类似于Spring对事务管理的支持.Spring Cache是作用在方法上的,其核心思想是这样的:当我们在调用一个缓存方法时会把该 ...
- Spring Boot 菜鸟教程 application.properties 常用配置
SPRING CONFIG (ConfigFileApplicationListener) spring.config.name 配置文件名称,默认为application spring.config ...
- docker: read tcp 192.168.7.235:36512->54.230.212.9:443: read: connection reset by peer.
在学习rancher的时候去下载rancher/agent镜像的时候,出现报错:docker: read tcp 192.168.7.235:36512->54.230.212.9:443: r ...
- Idea自带工具解决冲突
1:产生冲突 2:解决冲突 解决冲突具体操作: 手动合并代码: 此时点击的是local的>:点击changes的X则合并效果为: 也可以两侧都点击>.结果为: 也可以都点击X,结果为: 最 ...
- 【js】横/纵向无缝滚动
1.纵向无缝滚动(类似淘宝) ps:存在一个问题,当鼠标移入时,未关闭定时器 <!DOCTYPE html> <html> <head> <meta char ...
- java kafka单列模式生产者客户端
1.所需要的依赖 <?xml version="1.0" encoding="UTF-8"?> <project xmlns="ht ...