Hi Chris, I agree with you. First, I will implement the parallel deployment, so my redeployments wont cause unavailability. Then, with a little bit of time and as soon as I have two separate Tomcats and a load balancer, I will forget about the parallel deployment because, as you said, the other solution is better and helps me with the redeployment as well.
I do have leaks, but fortunately they happen just when I stop the app, but not when it is already running. I mean, it doesn't get worse with time. On Tue, May 10, 2011 at 1:25 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mark, > > On 5/9/2011 9:53 AM, Mark Thomas wrote: > > On 09/05/2011 14:45, Brian Braun wrote: > >> Hey, that is great! I had never noticed that new feature! But the > >> documentation is so scarse, it hardly explains what is it about. But I > think > >> that will solve my redeployment issue :-) > >> > >> But I still need to think about hig availabilty when Tomcat itself > crashes, > >> or when I restart it. I guess I need clustering, but the documentation > is so > >> scarse and confussing...... > > > > The documentation is certainly brief and to the point. If you have > > specific questions, please ask them. It should also be consistent. If > > there are things that appear to be confusing tell us what they are. > > > > In Tomcat terminology, clustering == session replication. You can do > > load-balancing without Tomcat clustering. > > > >From what you have written, you need load-balancing but not clustering. > > +1 > > You don't need session replication, failover, etc... you just need a > single request to (nearly) always hit a running server and return a > valid response. > > Apache httpd + mod_jk (or mod_proxy_ajp or mod_proxy_http) + multiple > Tomcats should do the trick. Feel free to layer parallel deployment on > top of that, though with your requirements and an lb the parallel > development doesn't really buy you anything. > > You should check to see if your webapp is leaky across webapp restarts > (with Tomcat continuing to run) because you could bringing-down the JVM > if your webapp does not undeploy cleanly /and/ it's got a memory leak. > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk3Jgv8ACgkQ9CaO5/Lv0PDfowCeP0R+7tuqM4DL2J1Jo9k+fyzl > 3pQAnA2DNg9OsMt0bKeDikcNvs/lwzxj > =5CIi > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
