Yes - they are. (as I stated in my original post)
Martin Gainty wrote:
check your unpackWARS and autoDeploy parameters are both set to 'true' e.g.
$TOMCAT_HOME/conf/server.xml
<Host
unpackWARs="true" autoDeploy="true"
HTH
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.
Date: Sat, 23 Aug 2008 23:40:06 +0300
From: [EMAIL PROTECTED]
To: users@tomcat.apache.org
Subject: Re: Tomcat does not unpack WAR file (Tomcat 5.5.20)
Thanks Johnny
On the production server, Tomcat is actually being started up by another
'parent' application. Since this does not appear to be a (pure) 'Tomcat'
issue, I will take it up with the guys who manage the 'parent' app.
Thanks for the assistance.
Johnny Kewl wrote:
----- Original Message ----- From: "Peter" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Friday, August 22, 2008 4:07 PM
Subject: Tomcat does not unpack WAR file (Tomcat 5.5.20)
Hi
When I drop a WAR file into the webapps folder on my dev machine -
running Tomcat 6.0.16 - Tomcat unpacks it on startup.
When I do the same on the production box - running Tomcat 5.5.20 -
nothing happens.
The WAR file that I am deploying is ROOT.war; there is a
corresponding ROOT.xml under conf\Catalina\localhost. (I'm not sure
if those details have any bearing on the problem - according to one
archived post, there may be a connection.)
On both machines, the <host> tags look identical:
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">
Any assistance would be appreciated. :)
Pete
--
Peter Cimring
Software Developer
(: +972 52-545-9364
*: [EMAIL PROTECTED]
Pete, nothing comes to mind, you seem to have the bases covered...
One possibility is that the existing ROOT web ap is busy...
Maybe a thread running or something... TC will not start up the new
guy, if the old one cant let go..
possibly from the manager console /manager/html tell the old one to
undeploy first maybe...
Also just make sure from you dev environment that the ROOT context
path is ""
really empty and not "root" which it maybe doing... wild guess ;)
---------------------------------------------------------------------------
HARBOR : http://www.kewlstuff.co.za/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm
---------------------------------------------------------------------------
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Peter Cimring
Software Developer
(: +972 52-545-9364
*: [EMAIL PROTECTED]
"/"Any sufficiently advanced technology is indistinguishable from
magic."/ - Arthur C. Clarke
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Be the filmmaker you always wanted to be—learn how to burn a DVD with Windows®.
http://clk.atdmt.com/MRT/go/108588797/direct/01/
--
Peter Cimring
Software Developer
(: +972 52-545-9364
*: [EMAIL PROTECTED]
"/"Any sufficiently advanced technology is indistinguishable from
magic."/ - Arthur C. Clarke
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
