-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ahmed,
On 12/30/11 12:41 PM, S Ahmed wrote: > If I have a running application, and I redeploy, is it possible to > keep the server live or does it have to shut-down and re-load? Any > gotchas with doing this on a busy server? If you just re-deploy, there will be a short interval where your clients may get 404, 400, or other errors. If you use Tomcat's parallel deployment feature, you can deploy a /second/ (or even third, etc.) copy of your webapp: old sessions will go to the old version and new sessions will go to the new one. Once the old sessions are all dead, you can undeploy the old copy. Just make sure your two versions are compatible with each other in certain areas, such as database schema :) > Also, I have been reading that if you don't probably clean things > up in a web app, there is a strong possibility that the class > loader will not be destroyed when re-deploying and result in OOM > errors potentially (if you redeploy frequently etc.) True. > How can you avoid this situation? Fix your webapp to properly clean things up. Tomcat includes some features to avoid problems with JRE classes not behaving correctly. See the JreMemoryLeakPreventionListener documentation for more information. > Is the [foolproof] method to start/stop the tomcat service? That's what we do, but in an ideal world, you should be able to re-deploy as much as you want. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk79++AACgkQ9CaO5/Lv0PAy+gCeK+18DDZ/9z8sAkZ8wGbv02/g MhoAn3lOD2dK6qKe56JVCLCsxa5iKmbt =FDDS -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org