ansaurus

Question

JBoss5: Cannot deploy due to java.util.zip.ZipException: error in opening zip file

Answer 1

A:

Are you able to open the ear file outside of JBoss (using WinZip or WinRAR)? It could be that the zip file is corrupted.

You could try writing a little test program using java.util.zip.ZipFile.open() and see if you can debug this in a more isolated situation.

Andy White 2009-03-14 18:08:12

Yes, I can open the EAR file. And it shows all the contents :/But I don't know where the problem arises. The EAR is created by eclipse.

Andreas 2009-03-14 22:34:48

What is eclipse using to create the EAR file? Are you using the Ant "ear" task? <ear destfile="blah.ear" ...

Andy White 2009-03-18 04:16:30

Answer 2

A:

Could this be a permissions issue? I see you're running under Mac OS. When you successfully open the EAR file, what user are you running as? When you run JBoss, what user does it run as? Does it have read access to the file?

Eddie 2009-03-15 00:24:36

No, that wasn't the reason. Changed to 777 and didn't work either.

Andreas 2009-03-15 10:11:08

I justed noticed that the ear and the war files seem to be regular files. How come?

Andreas 2009-03-15 11:17:59

What do you mean regular files? Do you mean they are uncompressed? Otherwise, yes, a ZIP file is just a regular file.

Eddie 2009-03-15 18:15:20

Answer 3

A:

I have the same error under windows XP, I believe JBoss runs with my user permissions, which is admin rights. Any ideas?

2009-03-30 09:05:54

Answer 4

+1 A:

I've seen this when FTP'ing a file with transfer mode set to ASCII instead of binary.

Damo 2009-03-30 09:27:15

Answer 5

A:

I also have this, but when I add an maven-war-plugin and maven-ejb-plugin to my projects everything works again...

2009-03-31 05:40:21

Answer 6

A:

Same problem with Jboss 5.0.0.GA, Eclipse 3.4.1 on Windows XP. I tried to install the war and ejb maven plugin, but it did nothing. I can't publish with jboss, nor export my project as an EJB Jar File. I got the ZIP error in both cases :

...
Caused by: java.util.zip.ZipException: ZIP file must have at least one entry
at java.util.zip.ZipOutputStream.finish(Unknown Source)
at org.eclipse.jst.jee.archive.internal.ZipStreamArchiveSaveAdapterImpl.finish(ZipStreamArchiveSaveAdapterImpl.java:57)
...

Don't know how to solve this at all by now...

2009-03-31 13:25:47

Answer 7

A:

try install web tools platform (WTP) from the eclipse update... I heard that there was some kind of bug, you will need version 3.0.4. I can't find the link, sorry... hope this will help!

2009-03-31 14:14:38

Answer 8

A:

I just discovered that if you don't specify a version number at the maven-war-plugin it will use some kind of alpha version. give it the version number 2.0, for me that worked.

2009-03-31 15:07:48

Answer 9

A:

I tried to change the version number of the maven-war-plugin to 2.0 but it did nothing. Actually, it seems for me that Maven has nothing to do with this. I just can't export a EJB Jar of my project. The publishing on Jboss thus doesn't work since it needs the Jar archive. I updated Eclipse to 3.4.2 but my issue's still there.

2009-03-31 16:06:35

Answer 10

+1 A:

Ok, I finally found the solution to my problem. It seems that there's a bug in Eclipse which prevent the creation of the .settings/org.eclipse.wst.common.component file. This file should be created when setting the EJB3 and Java6 facets in project properties.

Here is an org.eclipse.wst.common.component example file :

<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
    <wb-module deploy-name="project_name">
        <wb-resource deploy-path="/" source-path="/src/main/java"/>
        <wb-resource deploy-path="/" source-path="/src/main/resources"/>
        <wb-resource deploy-path="/" source-path="/src/test/java"/>
        <wb-resource deploy-path="/" source-path="/src/test/resources"/>
        <property name="java-output-path"/>
    </wb-module>
</project-modules>

The deploy paths must be defined in order to be able to create the EJB Jar file used by the server on deployment. Once created, Jboss publish the EJB module correctly.

2009-04-02 15:11:10

Answer 11

+1 A:

Sometimes this errors shows because of version of compilation of jar/ear difers from the jdk on the server.

2009-04-24 00:29:49

I've seen this too

sal 2009-06-23 18:51:18

Answer 12

+1 A:

I have experienced the same problem with JBoss 5.1.0.GA and Seam 2.1.1.GA. The JDK is java jdk1.6.0._07 for both Eclipse 3.5 and JBoss.

I was able to fix the problem. Maybe the origin of the problem has to do with you concrete case, or may not, but in any event, I thought that it may help.

I am creating the application EAR file using the build file that is included in the Seam installation examples; my build file it is a modified version of the one that comes with the bookings example. This sampl build file does an include to the build file that is common to all examples. It provides a lot of functionality that you can take advantage to create your distribution files.

The common build examples offers several fileset and path entries that you can override to include the libraries that are unique to your project.

Concretely, I was overriding "build.classpath.extras" and "ear.lib.extras".

I wanted to include a determined library in the EJB jar file that gets packaged into the EAR file (the jar file where my model and action classes are); so I just overrided "jar.extras" in my build file.

At that time is when I suffered this problem. Although my desired library in the root was copied into the root folder of the EJB jar file, apparently without problems, JBoss was dropping this error message.

So I just stopped using "jar.extras", and I moved the reference to the desired library to "build.classpath.extras": the effect of this action was that the the library was copied to the \lib folder of the EAR file. Now the application seems to work well, and the problem dissapeared.

Rafa Sanchez 2009-07-10 06:58:07

Answer 13

A:

Well, I'm facing the same problem for three days.. look at your classpath for files with .rar extentions or another type of these files, in my case, I remove a .rar file from my classpath and everthing works great.

Marcelo Daniel 2009-10-31 13:59:57

Answer 14

A:

I had the same problem, mine solution/problem was that I added the jar that was causing the problem as a EE dependency in my EJB. The jar was included in the EAR file, but wasn't in the org.eclipse.wst.common.component correspondent file. I added the dependency in the EAR file, and my problem was solved (At least I think, I had a problem after doing this with eclipse, but when I solve it, the publish went fine).

Pedro Gomes 2010-02-03 23:48:08

Answer 15

A:

I had the same problem on my Mac. My windows dev machine (client at work :-/) is too slow to run GateIN and eclipse so I installed GateIN on my Macbooc Pro and let eclipse copy the ear to it when built. I saw on the console: exception in the zip.

So I decided to investigate if I could perhaps open the archive using Stuffit Manager. The moment I opened it, apparently the file got 'touched' somehow and the GateIN scanner, detecting the change immediately redeployed, this time without error. So I guess that the Mac was simply too fast to try to redeploy before the ear was fully copied... If you have a problem, just use the touch command...

Lorenzo 2010-05-12 16:11:09

Answer 16

A:

The problem is most likely in the low level format of the ZIP file, possibly the result of JBoss trying to deploy a partially uploaded archive,

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:203)
    at java.util.zip.ZipFile.<init>(ZipFile.java:234

If you are uploading to a server over a slow link then try uploading the archive to a directory that JBoss does not monitor then move the archive into the deploy directory. The move will be an atomic operation or at least a lot faster than the upload.

I deploy archives by rsync'ing to ~/deployment-unit/ and then running a remote script over ssh to do the final move into JBoss's deployment directory.

Janek Bogucki 2010-05-12 17:20:59

Answer 17

A:

I solved this problem by running the server with the same JDK as i used to compile/build the EAR.

Sven 2010-05-26 16:06:20

Answer 18

A:

It is DEFINITELY a JBOSS bug!! If I get this error, I wait a few seconds, then copy the SAME ear again, without ANY change, and suddenly JBOSS DOES deploy it!! I mean common guys!! Last weeks I have been spending 80% of my time solving problems with JBOSS and Oracle; neither of which works as expected! These companies/organizations are responsible for an enormous loss of time/profit and an increase of stress!! I must admit, with pain in my heart, that most of these open-source packages do simply not work together good enough.

Lawrence 2010-06-07 01:18:07

Answer 19

A:

I've seen nested jars do this too (jar within another jar, or an empty jar). In my case it was a microsoft sql jdbc driver jar. The OP's seems to be TwitterPoCEJB.jar, by looking at the stack trace.

There are a lot of things that can cause this though, as mentioned previously simply a bad zip, etc..

If it is a nested jar problem, you can tell the VFS what locations contain nested jars, although by default the ./deploy directory is one of them, so anything in there should be fine (unless you've got a jboss-{something}.xml explicitly configuring things otherwise).

denny 2010-06-10 01:07:31

Answer 20

A:

I got a very similar error and it was due to the number of maximum open files being reached. I started the application after a ulimit -n 8192 and it was able to "unzip" the file.

Eric Darchis 2010-07-14 21:06:19

ansaurus

tags:

views:

answers:

JBoss5: Cannot deploy due to java.util.zip.ZipException: error in opening zip file

related questions