> I guess the only real thing I have going here is that, in my experience, > life has been 1000x better since we've moved to multi-server with > session replication and stickiness.
I bet it has. In spite of the few gotcha's I believe it is a better world. > The only complaint I've had for our public facing servers in > the last few months is an issue with our front end balancer. If a > CFHTTP request gets routed back to the same server making the request, > the load balancer fails the request. This _MAY_ be a routing issue if your web server has a WAN IP as well as an internal one. I have see similar problems where requests going from one load-balanced server come back through the load balancer to the same server get stopped. The fix I have found to be most useful is to put each server in its own host file. Normally, when you ping your domain, it resolves to your load balancer IP. Set up your server's host files so when you ping it from that server, it resolves to the local IP address of that server. In that way if will bypass the load balancer. I wish I knew more about the networking aspect of the whole thing but I don't. All I can offer is a post Ben Nadel has that I think is caused by the same issue: http://www.bennadel.com/blog/266-CFDocument-Errors-And-Resolving-DNS.htm ~Brad ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:311836 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
