Charlie, We use JRun clustering at my day job. We currently have several clusters in place. One handles public access requests. It consists of 4 machines, about 60 applications, and handles between 80-100k ColdFusion template hits daily. This has been in place for about a year now and has worked very well for us. The reason we went this route is that (our) load balancers had a hard time catching the fact that CF had died... mostly it just cared that IIS was available. Customers would call and complain that their application was unavailable "all day" (aka, any outage totaling more than 5 minutes) , and we (the CF Admins) would be in yet more trouble again. We also had the complication that each of these outages required that we drive to the data center to work on the affected machine. Moving to clustering has all be eliminated those calls and our need to go to the data center.
We also have a second cluster of 4 machines, about 40-50 apps, and about 40k CF templates daily. All are set to use sticky sessions, round robin, and also use J2EE session variables. The only time I've had an issue with this setup is for our lone MachII application. I don't know if it's typical for a MachII app, but the application and session scope variables required were astronomical. Everything, every display method, every action, was stored in a shared scope. That application moved to a dedicated server, and with it no longer being clustered, now has uptimes measured in weeks instead of 24 hour periods. Matthew Williams Geodesic GraFX www.geodesicgrafx.com/blog ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade to ColdFusion 8 and integrate with Adobe Flex http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:291910 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
