Yeah I stop the webapp and undeploy it before doing the redeploy so I don't think this is the issue. Unless the sessions are still persistent even after I've undeployed, which I don't think is the case.
-----Original Message----- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 9:37 AM To: Tomcat Users List Subject: Re: Load WARs Via The Manager App I know you cant deploy a webapp (when there are active sessions on the original webapp) so If you stop the webapp then re-deploy the webapp you should be abe to redeploy correctly M- ********************************************************************* This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <users@tomcat.apache.org> Sent: Wednesday, September 20, 2006 11:28 AM Subject: Load WARs Via The Manager App 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 --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
