What's your server platform, Windows or Linux? I had a really bad experience (ok, maybe not bad but extremely trying) with clustering CF on JRun on Redhat Linux. Granted, this was CFMX 6 (and whatever JVM version) five years ago so things should have improved by now, but we had to throw an inordinately large amount of RAM at the whole thing to make it stay up for more than two days. We had two honking servers (don't remember the exact specs now) and were running two instances of CF on each (supposedly it was faster with two instances) and had all four instances clustered, sticky sessions, memory object failover, and all. Eventually the Java heap would just fill up and the entire box would lock up. We would have to power-cycle the hardware to get it to work again for another two days. Eventually we shoved enough RAM in that it was stable but it wasn't pretty for a while.
On Tue, Oct 21, 2008 at 9:55 AM, Cameron Childress <[EMAIL PROTECTED]>wrote: > The J2EE clustering in the CF Admin is just a tool to manage the underlying > J2EE server, which by default is JRun. Unless you have a business reason to > run CF on something else, I usually would just stick to JRun. An argument > could be made that you get speed improvements from other J2EE platforms, but > there is more overhead and knowledge required in managing those. JRun > installs by default and "just works". Both sticky session and session > replication work with JRun. > -- Howard Fore, [EMAIL PROTECTED] "The universe tends toward maximum irony. Don't push it." - Jeff Atwood ------------------------------------------------------------- To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
