On 2/1/06, Tony Hicks <[EMAIL PROTECTED]> wrote: > I had an application that worked very well on one server, but growth required > we move to a larger server arrangement with two web servers. > > Of course the servers couldn't share memory so session variables no longer > really worked. I implemented client variables and the scope request.session. > > As I understand it.. all that is required for this to work is at the > beginning of the application, I should create request.session scope and load > it with data from the client.session scope via WDDX.
I've done this -- it can be a performance dog on the individual server, but it does allow for cheap scaling out with N servers. I'd honestly think about buying a low-end load-balancer with sticky sessions and seeing if distributing the load that way helps. But that's another topic... > From that point, I can read client.session with no need for scoping. > The site works perfectly, except when the load balancer presents a different > server. The user is logged out and loses all session data. > > Oh, my application uses "site_storage" (a dsn) as a client store and it on an > SSL connection. (A secure cert for each server). > > What am I missing? I'd check to make sure that in your <cfapplication> tag that you're using *domain* cookies (setDomainCookies="true"). Otherwise, the client cookie is stored for the particular web server (eg web01.domain.com vs web02.domain.com) -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:231070 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
