> I'm always a fan of not doing anything you don't have to. 
> There's no question that you will increase the performance of 
> your application by disabling the auto-deployment features of 
> Tomcat. The difference may be undetectable, but it's a simple 
> change, requires virtually no testing, and is guaranteed to 
> reduce the amount of work that Tomcat does regularly. What's 
> the downside?

Aggreed.

> 
> >> If you are using auto-deploy, then the context name is the 
> WAR file 
> >> name without the ".war" extension. So, for instance, foo.war is 
> >> deployed into "/foo". The special name ROOT.war will 
> auto-deploy to 
> >> "/".
> > 
> > Would auto-deploy ignore "context path" if specified in the 
> > META-INF/context.xml ?
> 
> If you use auto-deploy and you have a WAR file or directory 
> in the "webapps" directory, then any "path" attribute you 
> have in your <Context> element will be ignored (or, worse, 
> confused and used ion some weird way). Perhaps this is a 
> problem with your deployment.

That explains a lot, I have recommended that we drastically rethink our
deployment methodology


> 
> > What I am not sure about is how mod_jk would tell apache that the 
> > application is not available and if it would do so at all. We are 
> > seeing 404 errors while a new version of an application 
> gets deployed.
> 
> IIRC, Tomcat issues something like a 503 "Unavailable" 
> response when the application is undergoing a deployment. You 
> ought to be able to use an ErrorDocument directive to display 
> a "we're restarting" page to your users.

We are only a middle man, in that we provide a xml interface for other
website to search our database. We don't want any errors at all or downtime.
We get about 30million search requests a day so any downtime has significant
impact on clients.


> 
> I wouldn't have expected a 404 error. Then again, if you are 
> deleting the files yourself instead of having Tomcat do the 
> undeploy-redeploy cycle itself, then you could be seeing weird things.
> 
> > The safest way is to make the lb_factor 0 while deploying and then 
> > changing it back to x when the application has finished deploying.
> 
> That sounds like a horrible hack. :(

I probably aggree, reason being why I have asked if anyone knows about a
better way to do this.

Regards



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

Reply via email to