Tomcat: Deploying new verson without site downtime
We have running application on a server with Apache HTTP server in front and Tomcat server behind it as a servlet engine. When we deploy a new version of the application on Tomcat server, we have to shutdown the site (application context), deploy a new version (DB updates + new WAR) and start the server afterwards. Also, there are some backup things done before each deploy and initial testings after starting the application again, so this all make our site not available from 10 to 30 mins (sometimes even more).
Is there some deployment strategy with the server environment, like I have described above, for deploying a new version, so that we do not have site downtime? (Please, also reconsider of possible data changes in DB during a deployment of a new version, handling open HTTP session which started before deployment...)
Is there some deployment strategy with the server environment, like I have described above, for deploying a new version, so that we do not have site downtime? (Please, also reconsider of possible data changes in DB during a deployment of a new version, handling open HTTP session which started before deployment...)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It is not what I was looking for but nobody else, except you, responded. So you get all the points. :) Thank you, anyway. Regards
ASKER
Thank you for your comment. We already do the similar procedure like you wrote. It is an interesting idea, though, to schedule a job which will execute the shell script or ruby code to perform the deployment at some time around midnight.
But I would like to have a solution which will result in no site downtime. How it can be managed tha session could be shared among differnet Tomcat instances, or how that session replication could be achieved?
Any tips, examples, URLs?