On 24/02/2014 09:20, satish jupalli wrote: > Hi, > > What are the best practices for upgrading the tomcat given the fact that > they are no direct security patches available. > > Specially with the environments where there are large instances of Tomcat > servers running it is challenging to upgrade these servers manually in all > the systems. > > Are there any best practices defined for doing this given the frequency of > security patches being applied on Tomcat (Leave alone JDK patches)
Use a separate $CATALINA_HOME and $CATALINA_BASE. Upgrading should then be as simple as: - modify the init.d script to point to the new $CATALINA_HOME (you can safely use the new Tomcat version to stop the old one). - stop the instance - start the instance You can use rsync to have multiple servers all pick up the new CATALINA_HOME (note you don't want to replace the old one with the new one, you need to have multiple CATALINA_HOMEs alongside each another). You could even use rsync to update the init.d script. You could probably go further still with the automation and have it handle the restart too but how best to do that for your environment (if indeed it even makes sense to go further) is going to vary from installation to installation. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
