tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leon Rosenberg <>
Subject Re: High Availability in Tomcat?
Date Mon, 09 May 2011 10:03:58 GMT

well, you provided not that many infos, but the usual way of doing
this is to put multiple standalone tomcat instances behind a soft- or
hardware loadbalancer (whatever your budget allows) and to make the
app stateless, with cookie stickiness and failover.
However, this will probably not make the site 100% available (which
btw no site in the world is, not even google),
since you will have at least node failure detection times (usually 3
retries with 10 seconds timeout) and so on.
However, you can reach 99,9X pretty easy with this scenario.


On Mon, May 9, 2011 at 6:17 AM, Brian Braun <> wrote:
> Hi,
> I'm about to launch a service on the internet, using Tomcat 7. This service
> should be available 24x7, it should never be unavailable (or virtually
> never). However, I will definitely be improving and correcting my app
> frequently, so I will have to republish the WAR file very often. Not even
> considering the fact that my app has leaking problems (that's another story)
> and therefore I will have to restart Tomcat itself, republishing the app
> will make it unavailable for at least 10 seconds while I do it.
> I'm thinking that I need to create a Tomcat Cluster. Is that the way to go?
> Any opinions?
> Another idea would be to have two tomcat installations, and to change the IP
> my domain points to, to the IP that goes to that other Tomcat instance. But
> changing the IP takes some time and I would have to wait until I think that
> the DNS servers have updates the new IP, that would be slow and unreliable.
> Thanks in advance,
> Brian

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

View raw message