Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What's the best practice for hot-redeployment of WARs to Tomcat? Say that I have a webapp that serves a long-running type of user (logs in in the morning, uses all say), and want non-stop redeployment of the app where the current users can continue to be logged in but new sessions gets created against a redeploy war. My best guess would be using a loadbalancer and two sets of Tomcat instances, but whats the best practice and best software to do this (current environment is based on Ubuntu, Tomcat and Nginx.

share|improve this question
up vote 4 down vote accepted

Use Tomcat 7's hot deployment, in which your updated app runs alongside the current version. New sessions will use the new version, established sessions will use the current version. However, keep in mind that most security best practices want you to disable hot deployment.

share|improve this answer
I agree. If your plan is to hot-redeploy, then your development team needs to design for that in mind. Otherwise, lots of things can go wrong, and its better to cold deploy. – djangofan Sep 2 '11 at 21:33

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.