java.util.zip.ZipException: invalid LOC header (bad signature)

简介: java.util.zip.ZipException: invalid LOC header (bad signature)

记录下最近遇到的一些记录的东西:

  项目中引用消息中间件,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可能不会下载成功,会一直报该异常

 

标签: 异常

目录
相关文章
|
5月前
|
前端开发 Java 数据库连接
Spring Boot 升级 3.2 报错 Invalid value type for attribute ‘factoryBeanObjectType‘: java.lang.String
Spring Boot 升级 3.2 报错 Invalid value type for attribute ‘factoryBeanObjectType‘: java.lang.String
|
5月前
|
Java 应用服务中间件 Spring
SpringBoot出现 java.lang.IllegalArgumentException: Request header is too large 解决方法
SpringBoot出现 java.lang.IllegalArgumentException: Request header is too large 解决方法
212 0
|
5月前
|
前端开发 Java 应用服务中间件
【异常解决】java程序连接MinIO报错The request signature we calculated does not match the signature you provided.
【异常解决】java程序连接MinIO报错The request signature we calculated does not match the signature you provided.
402 0
|
5月前
|
SQL Java 数据库连接
解决bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: ORA-00911: 无效字符
解决bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: ORA-00911: 无效字符
119 0
|
5月前
java.lang.IllegalArgumentException: Invalid character found in method name
java.lang.IllegalArgumentException: Invalid character found in method name
159 0
|
5月前
|
SQL Java 数据库连接
解决bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: ORA-00911: 无效字符
解决bad SQL grammar []; nested exception is java.sql.SQLSyntaxErrorException: ORA-00911: 无效字符
81 0
|
5月前
【已解决】nested exception is java.sql.SQLSyntaxErrorException: ORA-01722: invalid number
【已解决】nested exception is java.sql.SQLSyntaxErrorException: ORA-01722: invalid number
64 0
|
8天前
|
Java 关系型数据库 MySQL
如何用java的虚拟线程连接数据库
本文介绍了如何使用Java虚拟线程连接数据库,包括设置JDK版本、创建虚拟线程的方法和使用虚拟线程连接MySQL数据库的示例代码。
20 6
如何用java的虚拟线程连接数据库
|
4天前
|
监控 Java Linux
Java 性能调优:调整 GC 线程以获得最佳结果
Java 性能调优:调整 GC 线程以获得最佳结果
34 11
|
11天前
|
Java 数据库 UED
Java的多线程有什么用
Java的多线程技术广泛应用于提升程序性能和用户体验,具体包括:提高性能,通过并行执行充分利用多核CPU;保持响应性,使用户界面在执行耗时操作时仍流畅交互;资源共享,多个线程共享同一内存空间以协同工作;并发处理,高效管理多个客户端请求;定时任务,利用`ScheduledExecutorService`实现周期性操作;任务分解,将大任务拆分以加速计算。多线程尤其适用于高并发和并行处理场景。