I get back to this discussion beacuse I was brainstorming again on it, and found that the already present class loader may actually be able to do this alone. My thought was: if Tomcat is capable of managing different application contexts under its "work" folder, and have them run different applications with different class versions inside their classes/lib, probably it may implement automatic application updates by createing different application contexts behind the scene. I see this scenario: - Tomcat is running my webapp - People have sessions on it, and Tomcat has its application context on my webapp - I place new jar files/classes - Tomcat detects, and instead of reloading and invalidating current sessions, it will keep current sessions on the old application context, until they reach 0 sessions - Meanwhile it may create a new application context to run new sessions How hard would it be to make this true in Tomcat? Is there any other Java WebApp Container capable of doing this? Gabriele. Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 028243880 Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY http://www.sonicle.com ---------------------------------------------------------------------------------- Da: Christopher Schultz A: Tomcat Users List Data: 3 maggio 2010 15.57.57 CEST Oggetto: Re: Updating webapps classes -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter, On 4/30/2010 10:33 AM, Peter Crowther wrote: In normal use, Tomcat1 is running. The load balancer directs all users to Tomcat1. Tomcat2 could even be stopped. I would say that "normal use" would include both (or however many) instances running in parallel. When it's time to upgrade, you mark one or more nodes in the cluster as "don't send any new users to this node" and wait for all the users on those nodes to complete their work. After that, Peter's scenario is exactly the same. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkve1mUACgkQ9CaO5/Lv0PAOhgCfRCZLdT0flr3es5Oc5IpCCNNl bokAn1F22eum4C6vhHoEv2LjQXee/9uk =IpQb -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
