2 Replies Latest reply on Jul 24, 2002 4:34 PM by vlevine

    invalid LOC header / jzentry == 0

    stevee

      I get this error every time I redploy. If I start and stop jboss then everythings ok.

      I'm using jdk1.4, and got a similar (but slightly different error) on jdk1.3.*

      I'm not running out of diskspace. I can unzip the ear, that war and the jar with winzip.

      Can anyone help?

      java.lang.InternalError: jzentry == 0,
      jzfile = 199696304,
      total = 91,
      name = C:\Documents and Settings\xxxx\Local Settings\Temp\Jetty__8
      080___yyyy\webapp\WEB-INF\lib\client.jar,
      i = 91,
      message = invalid LOC header (bad signature)
      at java.util.zip.ZipFile$2.nextElement(ZipFile.java:303)
      at java.util.jar.JarFile$1.nextElement(JarFile.java:200)
      at org.apache.jasper.compiler.TldLocationsCache.tldConfigJar(TldLocation
      sCache.java:234)
      at org.apache.jasper.compiler.TldLocationsCache.processJars(TldLocations
      Cache.java:207)
      at org.apache.jasper.compiler.TldLocationsCache.(TldLocationsCache
      .java:139)
      at org.apache.jasper.EmbededServletOptions.(EmbededServletOptions.
      java:350)
      at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:265)
      at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:225)

      at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHa
      ndler.java:414)
      at org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationC
      ontext.java:446)
      at org.jboss.jetty.Jetty.deploy(Jetty.java:405)
      at org.jboss.jetty.JettyService.performDeploy(JettyService.java:244)
      at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:30
      0)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:678)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:671)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:513)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481)
      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
      sorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea
      nDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy4.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
      tScanner.java:405)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
      canner.java:515)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
      loop(AbstractDeploymentScanner.java:202)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
      run(AbstractDeploymentScanner.java:191)

        • 1. Re: invalid LOC header / jzentry == 0
          vlevine

          I'll second this. I'm using jdk1.4.0_01 on Win2K. JBoss 3.0 with Jetty(obviously)

          • 2. Re: invalid LOC header / jzentry == 0
            vlevine

            See bug No. 4615343 on java.sun.com. It does not explain, however, the fact that the same file is perfectly valid after the JBoss restart, hence it is not a broken zip/jar file.

            Could that be some state stored (for example, CRC) which is failing, naturally, against a new version of the jar file. Killing JBoss resets the state and next deployment is going fine.