The Tomcat 5 server provides built-in support for clustering and session replication. This first article in this series will provide an overview of session persistence and the inner works of session replication in Tomcat clusters. I will discuss how the session replication process works in Tomcat 5 and the replication mechanisms available for session persistence across the cluster nodes. In part two, I will discuss the details of a sample Tomcat cluster setup with session replication enabled, and compare different replication scenarios.
Clustering has become one of the most common and most emphasized features of J2EE application servers, because, along with load balancing, it is the fundamental element on which the scalability and reliability of an application server rely.
Connect Tomcat servers to Apache and to each other to keep your site running
SummaryBy Graham King
If you run only one instance of Tomcat, you lose requests/sessions whenever you upgrade or restart your site. In this article, author Graham King presents simple steps for connecting a pair (or more) of Tomcats to Apache using the JK2/AJP (Apache JServ Protocol) connector and to each other using Tomcat 5's clustering capabilities. Any of the Tomcat servers can be stopped or started without affecting users. With an Apache/Tomcat cluster in place, you can easily adjust your configuration for a range of load-balancing and failover scenarios. (2,000 words; December 20, 2004)