Forum Discussion
Hi - to be brief - if you are using either no persistence, or source IP persistence, then a given client session (from the web server) will remain on the same application server for the duration of the TCP session, regardless of any idle periods.
My point was about the persistence timeout on the "source address affinity" persistence profile - the default is 180 but it can adjusted - and how that setting can be affect long running/idle sessions.
I think what I am hearing from you is that you only require TCP level persistence which is a default when you don't have a persistence profile (or source IP). I think you do not need to enable any persistence profile at your application tier and you will get the behaviour you want - each TCP session will be balanced separately and will stay on the same server.
- Ofelia_Carter_2Feb 08, 2016NimbostratusHello, I am having the same issue as described in this thread. Except TAC suggested I create a persistence profile for the WEB and APP virtual and apply it to teach along with HTTP. Using Source Addr Affinity/source addr It is not working for me. Any other feedback, greatly appreciated. thank you,