tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: High Availability in Tomcat?
Date Tue, 10 May 2011 18:25:03 GMT
Hash: SHA1


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.


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
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message