Thanks Robin, I'll run a few more test today and keep you posted. Jason Sheedy Senior Web Developer Voice International Limited
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robin Hilliard Sent: Wednesday, 1 December 2004 3:22 PM To: CFAussie Mailing List Subject: [cfaussie] Re: CFMX/JRun Clustering Jason Sheedy wrote: > Hi Robin, > > I found this in the jrun docs under the heading 'session replication', which > seems to suggest that the sessions are only replicated after each request. > > http://livedocs.macromedia.com/jrun/4/JRun_Service_Pack_1_Guide/4relnotes5.htm > > Session replication > > The following issues related to session replication are not fully explained > in the JRun 4 documentation: > > * Session replication only happens at the end of a request when > setAttribute or removeAttribute is called on the current session. The only > time you must be aware of this feature is when making a change to an existing > attribute. > > > 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. Hi Jason, 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. I was talking to Mark Blair about this, he thought the same thing as me (that a server has to reload session info when it starts) for the same reasons (replication would be very impractical if it didn't) but again it hasn't been confirmed. Is it possible to test this with your setup? Cheers, Robin http://www.rocketboots.com.au b‹šç.®·§¶\¬¹» ®&ÞvÚ }«¬²'š±ªÜ+Þ¨¥j·!Š÷œ¢dèº{.nÇ+‰·¬zwZnV§‘é[h•æ¯yÇÚË"{~ºàIb²Û iéÊ&jà.²È1§+¢g‰ Þéh¥êì†Ûiÿùb²Û iéÊ&jï
