The solution to this problem is to make the ear/war "creation" as atomic
and quick as possible. One method would be to change your ant task
to produce the file under a temporary name, and have a subsequent
task in the same target to rename it to the actual ear/war file. This is
atomic on m
[Randahl Fink Isaksen]
> I am wondering if I am the the only one getting an error when deploying a
> new .ear (this happens often but not always):
>
> Auto-unpacking C:\(...)\project.ear... Error unpacking: IO Error: error in
> opening
> zip file
>
> Does anybody know why this happens, and is th
This started happening to me a lot starting with 1.4.5, but not before.
Jeff
>-Original Message-
>From: Thomas Pridham [mailto:[EMAIL PROTECTED]]
>Sent: Friday, March 09, 2001 10:36 AM
>To: Orion-Interest
>Subject: RE: Error unpacking: IO Error: error in opening
>
&
Randahl,
I've had some problems with unpacking .ear and .war files in the past.
These are really JAR (Java Archive) files, which are really ZIP format files.
I think the problem I had was because of the tool that I used to create the
.ear/.war. The problem could also be somewhat related to the
We also see this problem alot. My opinion is that while ant is still
copying over the file, Orion tries to open it, resulting in an I/O error.
Sometimes Orion retries to open it and other times not. The EAR-auto deploy
is quirky!!
Regards,
Tom Pridham
Software Engineer
http://www.Oakscape.com
