So you have set up your Railo cluster using Apache and Tomcat as described in the Clustering Railo with Tomcat and Apache article and as far as you know the cluster is performing exactly as expected, or is it? The problem is unless you actually check the tomcat instances you really don't have a clue if one of the Tomcat instances are down. Luckily there is a relatively simple way to set up a monitor to monitor your cluster.

[More]

Building on from the Clustering Railo with Tomcat and Apache article we set up the Railo Tomcat cluster but it was set up to send all requests on to Tomcat. While in a low traffic site sending every single request to Tomcat for processing may not be a big deal, you probably haven't gone through the trouble of setting up a cluster for a low traffic environment therefore, you certainly want to squeeze as much performance out of your available resources.

[More]

This post is a result of a request from a client of ours to have a Railo cluster. The original idea was to use jBoss but ended up settling on stand-alone Tomcat instead.

We are going to set up a "High-Availability" cluster with load balancing using Apache to perform the proxying, Tomcat as our servlet container and Railo to serve up our CFML. You notice that I placed high availability in quotation marks; this is because while automatic failover will be enabled our sessions won't be replicated to all nodes in the cluster. The reason we won't be replicating the sessions is mainly because of performance reasons.

[More]

I must admit that it was a bit of a struggle for me to get this all working. It ended up taking quite a few frustrating hours first trying to get mod_caucho to compile on SUSE 10 before I gave up and switch tack and went with Tomcat.

[More]