O'Reilly Open Source Convention
oreilly.comO'Reilly Network
Conferences International Safari: Books Online

Arrow Home
Arrow Registration
Arrow Speakers
Arrow Keynotes
Arrow Tutorials
Arrow Sessions
Arrow At-a-Glance
Arrow BOFs
Arrow Events
Arrow Exhibitors
Arrow Sponsors
Arrow Hotel/Travel
Arrow Venue Map
Arrow See & Do
Arrow Press
Arrow Mail List
Kids World

From the Frontiers of Research to the Heart of the Enterprise
O'Reilly Open Source Convention
Sheraton San Diego Hotel and Marina
July 22-26, 2002 -- San Diego, CA



Tomcat 4 Clustering Models and Implementations
Jason Brittain, CollabNet Inc.

Track: Java
Date: Friday, July 26
Time: 11:30am - 12:15pm
Location: Marina III

Eventually, one machine just isn't enough for high traffic sites that use Java servlets. Regardless of whether it's for better scalability or for fault tolerance, eventually your servlets will need to run on more than one server machine. To help you set up and maintain a clustered Tomcat 4 system, you should understand some of the details of the models and existing implementations of Tomcat 4 clustering infrastructure software.

  • Why Cluster?
    • High availability: Traffic too high for one server machine to handle.
    • Fault tolerance: You need either homogeneous or heterogeneous clustering.
  • The Many Ways of Clustering Tomcat 4
    • DNS Load Balancing (WAN solution)
    • TCP Hop (LAN solution)
    • HTTP Redirect (WAN or LAN solution)
    • Apache or 3rd party web server connector load balancing (LAN solution)
    • In-memory session replication (LAN solution)
    • In-database session clustering (LAN solution)
  • Tomcat 4 Clustering Implementation Options
    • mod_jk and derivatives
    • mod_backhand
    • Session replication options
    • mod_webapp (currently doesn't load balance)

Download presentation file

oreilly.com Home | O'Reilly Bookstores | How to Order | O'Reilly Contacts
International | About O'Reilly | Affiliated Companies | Privacy Policy

© 2001, O'Reilly Media, Inc.