How about using client variables instead, or setting up a CFMX jrun cluster on both servers and using jsessions.
Russ -----Original Message----- From: Brad Wood [mailto:[EMAIL PROTECTED] Sent: 20 October 2006 17:57 To: CF-Talk Subject: RE: Foundry Server Iron Our CIO wants our users to be logged in to our web app for 12 hours at a time regardless of activity. That means I have to allow someone to log in, walk away for their computer for 11 hours and 59 minutes, and then click on something and still be logged in (for another 12). Our load balancer REFUSES to keep a sticky connection for longer than 60 minutes for reasons no one has been able to explain to me yet. That causes a problem when people bounce to a different server after only an hour of inactivity, because our sessions are not shared between our production servers. This logs them out prematurely. ~Brad -----Original Message----- From: Russ [mailto:[EMAIL PROTECTED] Sent: Friday, October 20, 2006 11:34 AM To: CF-Talk Subject: RE: Foundry Server Iron Is this setting between requests? Are you saying your session time out in CF is higher then 60 minutes? Russ > -----Original Message----- > From: Andrew Tyrone [mailto:[EMAIL PROTECTED] > Sent: Friday, October 20, 2006 12:24 PM > To: CF-Talk > Subject: RE: Foundry Server Iron > > > -----Original Message----- > > From: Christine Davis [mailto:[EMAIL PROTECTED] > > Sent: Thursday, October 19, 2006 5:21 PM > > To: CF-Talk > > Subject: RE: Foundry Server Iron > > However, having said that... We really are interested if anyone has > > any insight, our tech folks require hardware load balancing and > > we're trying to support our user's request that we not require them > > to log in more > > than once a day. Because the sticky session expires on the load > > balancer after 60 minutes, the user is sometimes directed to a > > different server where they must log in again. This is apparently a > > world ending event that causes thousands of dollars in lost > > productivity... so, the > > search for a solution that doesn't involve changing our current load > > balancing methods is on... I love politics, it's a Dilbert world. > > Anyone have an "outside the box" kind of solution for me? > > It does indeed look like ServerIron allows the TCP age to only be between > 2 > and 60 minutes. > > How about sending a keep alive connection to the server using a timer > within each page of the application? If a session is in danger of > timing out, > hit > a generic timeout URL with a request to keep the session live on the load > balancers. > > Andy > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:257604 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
