1 Reply Latest reply on Sep 7, 2010 11:58 PM by dan.j.allen

    Problems with servlet containers

    swd847

      I have been trying to test seam-persistence in a servlet container (both jetty and tomcat), however I keep running into this exception:

       

      Caused by: java.util.zip.ZipException: error in opening zip file
              at java.util.zip.ZipFile.open(Native Method)
              at java.util.zip.ZipFile.<init>(ZipFile.java:114)
              at java.util.zip.ZipFile.<init>(ZipFile.java:131)
              at org.jboss.weld.environment.servlet.deployment.URLScanner.handleArchiveByFile(URLScanner.java:142)
      Caused by: java.util.zip.ZipException: error in opening zip file
              at java.util.zip.ZipFile.open(Native Method)
              at java.util.zip.ZipFile.<init>(ZipFile.java:114)
              at java.util.zip.ZipFile.<init>(ZipFile.java:131)
              at org.jboss.weld.environment.servlet.deployment.URLScanner.handleArchiveByFile(URLScanner.java:142)
      

       

      The zip that it is dying on is one of the libraries I have deployed to WEB-INF/lib, opening the zip manually works fine.

       

      I get this as part of weld-servlets scanning process in both tomcat and jetty with no detail message as to what is wrong with the zip, does anyone have any idea's?

        • 1. Re: Problems with servlet containers
          dan.j.allen

          I vaguely remember having this problem before, but I can't uncloud my memory.

           

          A couple of things that could help here. First, enable trace to get some debugging output from Weld and also list the versions you are using. You may want to start by seeing what you are doing differently from the in-container test case for Embedded Tomcat:

           

          http://github.com/arquillian/arquillian/tree/master/containers/tomcat-embedded-6/

           

          You should be able to run the tests simply by executing:

           

          mvn test

           

          If there is a discrepancy between what that test is validating and what you are encountering, it's an opportunity to make the test more robust.