There's a ton of information for setting up session replication and clustering
for cfmx6.1/7. There's an Adobe livedoc here:
http://livedocs.adobe.com/coldfusion/7/htmldocs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=ColdFusion_Documentation&file=00001774.htm
that describes how to do this. There's an article here:
http://www.adobe.com/devnet/coldfusion/articles/clustering_print.html on
devnet. There's an older document here:
http://www.talkingtree.com/blog/index.cfm/2004/2/25/No-Frills-Guide-CFMX61-Clustering
on the talking tree.
Basically, you need CFMX enterprise (and what follows is a real shallow
look at
what needs to be done). The easy route is to install CFMX in
multiserver mode.
This will give you one cfusion-ear already deployed as a JRun Server
instance.
If you're on CFMX 7, you can then use the Enterprise manager features
within the
administrator to deploy new instances/clusters. Otherwise, you need to
use the
JRun management console (which I actually prefer).
Once all of your instances and clusters are created/deployed, you would
then run
the "Web Site Configuration Tool" (which is really a shortcut to running java
-jar wsconfig.jar) so that you can configure IIS/Apache/etc. to be
connected to
a cluster/instance.
Things that are gotchas to look out for:
* You need to turn on J2EE session vars if you want to successfully
replicate
information across the cluster.
* You need to ensure that session replication is enabled for each
cluster when
the instance is created in the CF admin.
* Context roots can be a pain in the rear. If all of your sites are
hosted as
seperate domains, not so much an issue.
* The most informative logs for session issues are found in
{jrun_root}/logs.
Watch these logs carefully as they will let you know if the instances are able
to connect to each other. To be more specific, the {instance}-info.log only
contains clustering information. This information is also found in
{instance}-out.log.
* Flash gateways can only have one context root. Or, at least this was the
case in 6.1. I've not had to make this available, so I've not really messed
with it much.
* If the machines are NOT on the same subnet, you will probably have issues
with replication. You can use Unicast instead of Multicast for communication
betwixt the servers, but it is a long hard slog to make it work correctly.
Even then, it won't work if you have multiple clusters on the machines.
That being said, I have a total of 6 clusters, and 22 instances to
manage. The
only issues that I have are self imposed due to constraints on the environment
(bad things happen with session replication when JSessionIDs don't match the
servers serving the pages). The largest cluster consist of 3 machines,
hosting
2 clusters each. I've not seen anything detrimental happen due to session
replication, and we host multiple sites per cluster.
Matthew Williams
Geodesic GraFX
www.geodesicgrafx.com/blog
Quoting Brad Wood :
> Ah, I see what mean by "drain". In other words, it doesn't add any
> more users to that server, and just lets them disconnect one by one as
> they time out until no-one is left.
>
> That solution would be no good for us. Our application keeps the user
> logged in for 12 hours. It is used internally by our employees-- they
> come to work in the morning, log in, and stay logged in all day long.
> If we tried to "drain" a server, it would never drain. That is simply
> not an option if we need to remove a server during the day immediately.
> Please correct me if I am wrong, but from what I understand about
> sharing sessions across a cluster of software balanced servers is that
> if we WERE to kick someone off of one server and to another, their
> session and client etc info would follow them along with their cfid and
> cftoken to the new server.
>
> Am I making any sense at all here? I feel like I'm shouting in the wind
> or something.
>
> And I still haven't had a single person offer one shred of reading
> material (tutorials, step by step installs instructions, how to's) on
> the subject of installing enterprise and configuring session sharing
> across clusters etc. which was my original request... Does this stuff
> not exist?
>
> *sigh*
>
> ~Brad
>
> -----Original Message-----
> From: Eric Haskins [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 07, 2007 10:12 AM
> To: CF-Talk
> Subject: Re: installing CF Enterprise, Load Balancing Etc...
>
> Brad,
>
> Most Hardware balancers have options to allow the server to drain
> users
> on it by not allowing new sessions. Yes it will kick users on the server
> you
> are taking out of service if you do not allow it to drain. I can see how
> many sessions are active on each server in the farms.
>
> When we were using Cisco LD's we were using Clientvars so session info
> wasnt
> an issue.
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
ColdFusion MX7 and Flex 2
Build sales & marketing dashboard RIAâs for your business. Upgrade now
http://www.adobe.com/products/coldfusion/flex2
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:271907
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
