簡體   English   中英

無效的CEN標頭(錯誤的簽名)

[英]invalid CEN header (bad signature)

我在Java方面的工作還不是很多,但是我正在嘗試升級libabry。 我正在嘗試使用Maven在本地運行java google app引擎項目,並且收到錯誤/警告消息(如下所示)。

2018-05-17 14:39:55.050:INFO:oejs.Server:main: jetty-9.3.18.v20170406
2018-05-17 14:39:55.189:WARN:oejw.WebAppContext:main: Failed startup of context c.g.a.t.d.j.DevAppEngineWebAppContext@7995092a{/,file:///Users/user1/eclipse-workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/helloworld/,null}{/Users/asingh1/eclipse-workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/sap_gateway}
java.util.zip.ZipException: invalid CEN header (bad signature)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:225)
at java.util.zip.ZipFile.<init>(ZipFile.java:155)
at java.util.jar.JarFile.<init>(JarFile.java:166)
at java.util.jar.JarFile.<init>(JarFile.java:103)
at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:93)
at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:69)
at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:84)
at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122)
at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:89)
at org.eclipse.jetty.webapp.MetaInfConfiguration.getTlds(MetaInfConfiguration.java:409)
at org.eclipse.jetty.webapp.MetaInfConfiguration.scanForTlds(MetaInfConfiguration.java:326)
at org.eclipse.jetty.webapp.MetaInfConfiguration.scanJars(MetaInfConfiguration.java:143)
at org.eclipse.jetty.webapp.MetaInfConfiguration.preConfigure(MetaInfConfiguration.java:94)
at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:485)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:521)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:131)
at org.eclipse.jetty.server.Server.start(Server.java:422)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:105)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:389)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at com.google.appengine.tools.development.jetty9.JettyContainerService.startContainer(JettyContainerService.java:346)
at com.google.appengine.tools.development.AbstractContainerService.startup(AbstractContainerService.java:284)
at com.google.appengine.tools.development.AutomaticInstanceHolder.startUp(AutomaticInstanceHolder.java:26)
at com.google.appengine.tools.development.AbstractModule.startup(AbstractModule.java:87)
at com.google.appengine.tools.development.Modules.startup(Modules.java:105)
at com.google.appengine.tools.development.DevAppServerImpl.doStart(DevAppServerImpl.java:274)
at com.google.appengine.tools.development.DevAppServerImpl.access$000(DevAppServerImpl.java:47)
at com.google.appengine.tools.development.DevAppServerImpl$1.run(DevAppServerImpl.java:219)
at com.google.appengine.tools.development.DevAppServerImpl$1.run(DevAppServerImpl.java:217)
at java.security.AccessController.doPrivileged(Native Method)
at com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:217)
at com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:368)
at com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:45)
at com.google.appengine.tools.development.DevAppServerMain.run(DevAppServerMain.java:223)
at com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:214)
2018-05-17 14:39:55.201:INFO:oejs.AbstractConnector:main: Started NetworkTrafficSelectChannelConnector@43ee72e6{HTTP/1.1,[http/1.1]}{localhost:8080}
2018-05-17 14:39:55.212:INFO:oejs.Server:main: Started @1089ms
May 17, 2018 6:39:55 PM com.google.appengine.tools.development.jetty9.JettyContainerService startHotDeployScanner

信息:每1秒就對Web應用進行一次全面掃描。

Java版本:jdk1.8.0_172 Maven版本:3.5.3 appengine.target.version:1.9.63 maven-compiler-plugin:3.7.0(源和目標:1.8)javax.servlet-api:4.0.1

我試圖刪除.m2文件夾並進行mvn全新安裝

任何幫助表示贊賞! 謝謝。

謝謝大家的幫助! JAR文件在源代碼上很好。 我對我收到未簽名消息的源文件運行了jarsigner verify 在目標文件夾中的JAR文件上運行相同的命令時,出現“無效的CEN標頭(錯誤的簽名)”。 然后我搜索了在mvn構建期間損壞的JAR文件,然后找到了解決方案 在mvn生成過程中文件已損壞。 我從pom.xml文件中刪除了<filtering>true</filtering> ,並且停止收到錯誤消息。

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM