Damn this is strange.... I would expect Tomcat to protest... missing
class's... or something?
I'm now fascinated.... Michael if you like, you can send me the WAR... and
I'll see if I can get it to break on my system.
----- Original Message -----
From: "Michael Heinrichs" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Wednesday, May 09, 2007 9:30 PM
Subject: RE: WAR deployment incomplete (sometimes)
I thought I was being clear, but I will try again.
Tomcat is not running. In the scenario where the deployment has failed,
Tomcat has never been running. Tomcat is installed as part of another
application. The ROOT.war file is pre-installed under the webapps
directory. At this point, they are just files on disk. Then Tomcat is
started, the ROOT.war is detected, and unpacked. However, sometimes the
WAR is not completely unpacked. Tomcat completes startup, but because
the webapp's web.xml is near the end of the WAR file (i.e., this file is
not unpacked), the webapp does not initialize correctly. At this point,
Tomcat is running (i.e. it did not crash during unpacking), but the web
application is broken. To recover, stop Tomcat, delete the (incomplete)
webapp directory, and start Tomcat again.
-----Original Message-----
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 3:17 PM
To: Tomcat Users List
Subject: Re: WAR deployment incomplete (sometimes)
here is what happens,
your start copying in a large .war file, tomcat detects this file before
the upload is complete and starts expanding it,
tomcat receives a ZipFileCorrupted error (as the upload hasn't
completed) and aborts the deployment
you need to work around the fact that your upload is "taking time"
Filip
Michael Heinrichs wrote:
I don't see a consistent pattern, but it definitely happens on first
deployment. In my scenario, Tomcat is installed as part of a larger
product installation, with the WAR file under the webapps directory,
ready for deployment when Tomcat is first started. So the WAR is
intended to only ever be deployed once, and it's failing the first
time.
I have seen it fail a second time, so it's not just a new-install
issue
either.
To try to reproduce this problem, I wrote a script to repeatedly:
- stop Tomcat
- delete expanded WAR directory
- start Tomcat
- verify WAR expansion
The deployment never failed under these test conditions.
-----Original Message-----
From: David Kerber [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 11:39 AM
To: Tomcat Users List
Subject: Re: WAR deployment incomplete (sometimes)
I've occasionally seen this on 5.5.15 on Windows, but never thought
much
of it, just assuming it was a random glitch. It seems to be more
common
for me when I restart it quickly after stopping, and less often if I
let
it sit for 30 seconds or so before restarting.
Michael Heinrichs wrote:
I forgot to mention that (should it matter) I am running Tomcat
5.5.17,
on JRE version 1.4.2_12.
-----Original Message-----
From: Michael Heinrichs [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 09, 2007 10:43 AM
To: users@tomcat.apache.org
Subject: WAR deployment incomplete (sometimes)
Hello everyone,
I am having a problem with WAR deployment. I am performing a static
deployment: copying a ROOT.war under the webapps directory, and then
starting Tomcat (no other web applications). On most occasions, the
deployment is successful. However, occasionally the deployment does
not
succeed, and the WAR is only partially unpacked. Subsequently
stopping
Tomcat, deleting the expanded webapp directory, and starting Tomcat
again will (normally) result in a successful deployment. When this
happens, I see no exceptions in the logs. I've looked at the Tomcat
source responsible for WAR expansion, and found no clues.
I have begun collecting data to establish whether the unpacking
always
stops at the same point in the WAR, but only have one data point so
far.
I have verified that the WAR unpacking stops at a sequential point
(all
files before that point are unpacked, and all files after that point
have not been unpacked). In the single instance I have recorded,
unpacking stops between two similar, and unremarkable HTML files.
This problem has occurred on Solaris, Linux (Redhat), and Windows, so
this problem is not platform-specific.
I've searched the mailing list archives, and I can find no reference
to
others having the same problem. Can anyone offer an explanation or
solution?
Thanks,
Mike
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
