Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.0.0RC0
-
Fix Version/s: None
-
Component/s: Maven
-
Labels:None
-
Environment:Mac OS X 10.4.7
-
Number of attachments :
Description
This works on windows, but with a scanIntervalSeconds of 10 I always get this when it attempts to restart the webapp:
:WARN: failed ContextHandler@6ea3fe
{/,file:/Users/brett/scm/maven/archiva/maven-repository-webapp/src/main/webapp/}Exception in thread "Thread-3" java.lang.InternalError: jzentry == 0,
jzfile = 3270336,
total = 33,
name = /Users/brett/.m2/repository/org/apache/maven/repository/maven-repository-configuration/1.0-SNAPSHOT/maven-repository-configuration-1.0-SNAPSHOT.jar,
i = 33,
message = invalid LOC header (bad signature)
at java.util.zip.ZipFile$3.nextElement(ZipFile.java:429)
at java.util.zip.ZipFile$3.nextElement(ZipFile.java:415)
at java.util.jar.JarFile$1.nextElement(JarFile.java:217)
at java.util.jar.JarFile$1.nextElement(JarFile.java:216)
at org.mortbay.resource.JarFileResource.list(JarFileResource.java:233)
at org.mortbay.jetty.webapp.TagLibConfiguration.findTLDs(TagLibConfiguration.java:124)
at org.mortbay.jetty.webapp.TagLibConfiguration.configureWebApp(TagLibConfiguration.java:188)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1121)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:414)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:461)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
at org.mortbay.jetty.plugin.Jetty6PluginWebApplication.start(Jetty6PluginWebApplication.java:137)
at org.mortbay.jetty.plugin.AbstractJettyRunMojo$1.changesDetected(AbstractJettyRunMojo.java:354)
I know this was a known issue if the file changes while it is being deployed, but the file is never mid change when this happens, and it happens on every deploy.
Is it possible that it is because the file is open when it is copied over?
If there is nothing that can be done here in place, I'd suggest copying the jars to a temp location before adding them to the webapp, then monitoring the originals for modification and copying them again between the stop and start of the webapp.
wdyt?
Does this happen on the very first deploy? What changed that initiated the redploy? Was it the maven-repository-configuration jar itself or something else?