-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian,
On 4/11/2011 6:52 PM, Brian Braun wrote: > I have a new project, for a web service that must be running all the time. > It should never be offline, and if it does, my clients will leave me, so I > can not run this app in the same Tomcat installation. If you need 100% uptime, you'll need more than one server. If you have more than one server, don't restart all Tomcat instances at once. Instead, use clustering (which includes session fail-over) and re-start each Tomcat instance individually. That should ensure that no service interruption is ever encountered. In order to cluster, you'll need some kind of server out in front that can load balance and direct requests to one of several running Tomcat instances on the back-end. Don't forget to set up redundancy at that level, too. If you're going to run a lb, you can just do what we do and run each webapp in it's own JVM and Tomcat instance, and have the lb direct the traffic to the right place. The cluster isn't necessary in that scenario unless you truly need 100% uptime (which is impossible IMHO). The real question is why you have to restart Tomcat instead of just restarting the webapp itself. We separate ours for flexibility and isolation (one OOME doesn't bring-down all services, we can run different JVMs or Tomcat versions for each webapp, etc.). Why do you restart your entire JVM just to bounce your webapp? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2kdoIACgkQ9CaO5/Lv0PCgdwCeMbJN8pVk6jr+5897Llat5UxF el0AoIAzWQoS+UyffBmvH2xPcarOA2Hy =RmPT -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
