locked
F5 Load balancer losing stickiness inexplicably RRS feed

  • Question

  • ALL

    I'm new to the LB arena and this is the problem I'm having...Hopefully someone can shed some light...

    Have an F5 LB in front f 2 web servers running the my app. My problem is when a user logs into the APP through Web01
    ans it stays on a page 6-10 minutes, the App makes the user re-login. This should not happen since the app inactivity timeout is 20 minutes.
    I then turned to the web servers logs and found out that the user's session would somehow 'dissapear' forcing the user to the other web server
    thus forcing the user to re-login to the app. This is clearly a problem and the LB should 'hold' that session information and send the user back to the same server where the session was active. 1.- What could be terminating the session prematurely? and 2.- WHy could my LB not be 'sticky' long enough for the users
    to go back to the original web server? and 3.- How do I configure my F5 to be 'sticky' longer (at least the 20 minutes my app is already set to)

    THanks
    Thursday, August 27, 2009 8:00 PM

Answers

  • Apologies-- I'm not sure we'll be able to help out too much here-- if there is a question or issue specific to building and integrating HealthVault applications or devices, our APIs, the .NET SDK, etc, we can certainly help out.  But we're not necessarily the best experts for particular external app issues or external operations questions, like those involved with running a particular load balancer.

    If someone on the forum has some advice or suggestions, please hop in.  However, I just want to warn you up front that I don't know if we'll be able to answer your question here directly.
    Thursday, August 27, 2009 8:11 PM