tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From הילה <hilavalen...@gmail.com>
Subject Re: High Availability in Tomcat?
Date Tue, 10 May 2011 20:45:23 GMT
"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."

How can it be checked?



2011/5/10 Christopher Schultz <chris@christopherschultz.net>

> -----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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message