Hi All,

I have some questions about deploying WARs using Tomcat's built in
manager.  It seems that some of the times when we use the manager via a
web browser to deploy a new WAR file it will only partially install.
Meaning that the manager will return a list of the installed
applications and it will show our new application installed but the
'Display Name' is blank, even though there is a Display Name set in the
application's web.xml.  Also, at this point, if I try to hit the
application it will return an error and if I go and look at the expanded
WAR on the file system it will be missing files.  If I then undeploy and
reploy the same WAR it will usually get installed correctly, though I've
had times where I've had to reinstall again to get everything done
correctly.  Does anyone know why this is?  Or, does anyone have a better
way if deploying applications?  What are the recommendations for
deployment in production environments?

My guess is that Tomcat is trying to deploy the WAR file before it's
fully been copied over.  In our server.xml we have autoDeploy set to
true (as well as unpackWARs)

Here's a run down of our environment:
Our dev and test boxes are Suse Linux 8 (2.4 kernel, I know, we're
working towards upgrading to the 2.6 kernel) with Apache 2.0.55 talking
to Tomcat 5.5.9 via mod_jk 1.2.12.  I should note that when I'm using
the manager, I bypass Apache and mod_jk and go directly to tomcat via
the 8080 port.

Our production environment is Suse Linux 8 with two apaches talking to
two clustered tomcats via mod_jk.  All versions are the same as
dev/test.  

Thanks,

Scott

Reply via email to