We have an app written in a mix of JSP, servlets and struts across 3
instances of apache, tomcat and an RMI server. To say that it's a pile of
smelly stuff is an understatement, however it works (mostly) and our
customers depend on it. At least once a week though it crashes with out of
memory errors.
Until we can redesign and fix it we are looking for a way to keep it up. One
suggest has been to have two servers running with a common DB server, and to
use a load balancer to allow us to keep one server up whilst we boot the
other, then vice versa. Thus on a daily basis we can reboot both machines
whilst mainting a working system for the users.
Can anyone see any problems with this ? I'm concerned about issue realed to session management, etc.
I've had good luck using Apache and mod_jk configured with sticky sessions used to load-balance across multiple Tomcats. Works great. With Tomcat 5.0 you can do session replication so that you can even lose a Tomcat instance without missing a beat.
-Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
