Hi Sean, thanks for clarifying that. It was my understanding that that's the way it should work, but I just want to be certain. I think the network lag could be the only problem, so it may be good to give it a minute or so before shutting down the second server.
Jason Sheedy Senior Web Developer Voice International Limited -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Corfield Sent: Wednesday, 1 December 2004 3:43 PM To: CFAussie Mailing List Subject: [cfaussie] Re: CFMX/JRun Clustering On Wed, 01 Dec 2004 16:22:15 +1100, Robin Hilliard <[EMAIL PROTECTED]> wrote: > > This is a bit of a problem when doing maintenance. If I restart server A, > > to ensure that I'm not going to drop any sessions I have to wait for the > > session timeout length before I restart server B. > Yes, I read that as well and took it to mean that the sessions weren't > replicated during the request as their properties were set. There is certainly a network lag across servers so replication isn't 'instantaneous' but you shouldn't have to wait for session timeout to restart servers - you should be able to stop a server, do your maintenance, start it and then stop the next server in the sequence. I don't think that note in the documentation implies anything about the timing of replication, only the mechanics (that changes to session variables must be made explicitly through those methods). -- Sean A Corfield -- http://www.corfield.org/ Team Fusebox -- http://www.fusebox.org/ Breeze Me! -- http://www.corfield.org/breezeme Got Gmail? -- I have 1 invite "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
