java.util.zip.ZipException: invalid LOC header (bad signature)
2023-04-18 14:05:00 时间
记录下最近遇到的一些记录的东西:
项目中引用消息中间件,pom文件中添加了依赖,并maven-update,maven-install等,项目启动之后,一直报下面的异常。
Could not index class org/apache/activemq/artemis/api/jms/ActiveMQJMSClient.class at /D:/wildfly820Final_2/standalone/deployments/fucdn-admin.war/WEB-INF/lib/windq-artemis-jms-client-2.4.0-BETA9.jar: java.util.zip.ZipException: invalid LOC header (bad signature) at java.util.zip.ZipFile.read(Native Method) [rt.jar:1.8.0_181] at java.util.zip.ZipFile.access$1400(Unknown Source) [rt.jar:1.8.0_181] at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source) [rt.jar:1.8.0_181] at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(Unknown Source) [rt.jar:1.8.0_181] at java.util.zip.InflaterInputStream.read(Unknown Source) [rt.jar:1.8.0_181] at java.io.BufferedInputStream.fill(Unknown Source) [rt.jar:1.8.0_181] at java.io.BufferedInputStream.read1(Unknown Source) [rt.jar:1.8.0_181] at java.io.BufferedInputStream.read(Unknown Source) [rt.jar:1.8.0_181] at java.io.DataInputStream.readFully(Unknown Source) [rt.jar:1.8.0_181] at java.io.DataInputStream.readFully(Unknown Source) [rt.jar:1.8.0_181] at org.jboss.jandex.Indexer.verifyMagic(Indexer.java:433) [jandex-1.2.1.Final.jar:1.2.1.Final] at org.jboss.jandex.Indexer.index(Indexer.java:689) [jandex-1.2.1.Final.jar:1.2.1.Final] at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_181] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_181] at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_181] 17:37:05,015 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."fucdn-admin.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."fucdn-admin.war".STRUCTURE: JBAS018733: Failed to process phase STRUCTURE of deployment "fucdn-admin.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_181] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_181] at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_181] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018741: Failed to get manifest for deployment "/D:/wildfly820Final_2/standalone/deployments/fucdn-admin.war/WEB-INF/lib/windq-artemis-jms-client-2.4.0-BETA9.jar" at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.getManifest(ManifestAttachmentProcessor.java:78) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.deploy(ManifestAttachmentProcessor.java:65) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final] ... 5 more
这个主要的异常提示是:
java.util.zip.ZipException: invalid LOC header (bad signature)..
这个主要由于引用的maven依赖文件在maven仓库没有下载成功,需要将maven仓库中对应的文件删除之后重新下载。
如果不删除,一直maven-update或maven-install可能不会下载成功,会一直报该异常
相关文章
- 一文带你深入理解JVM内存模型
- JVM深度剖析:一文详解JVM是如何实现反射的?
- JVM整体架构与调优参数说明
- JVM 实战 OutOfMemoryError 异常
- 美团面试:熟悉哪些JVM调优参数,幸好我准备过!
- JVM 三色标记法与读写屏障
- JVM 运行时内存分代结构
- JVM底层原理解析,在这个开源项目里讲透了
- JVM虚拟机整体结构与对象内存分配解析
- 揭开JVM中TLAB中的神秘面纱
- CMS:听我的,生产环境上要这样配置JVM参数
- 面试必问的 JVM 运行时数据区,你懂了吗?
- 人工智能五种开发语言对比,选择哪个更好呢?
- JVM 君,你是不过分了
- JVM底层原理解析
- JVM是如何和“垃圾”发生关系的
- /和/*的区别记不住?我的答案保你终身难忘
- 为什么Spring仍然会是云原生时代优秀平台之一?
- 看完这篇后,别再说你不懂JVM类加载机制了~
- GraalVM下一代JVM到底是什么?