Forum Discussion
Kai_Wilke
Feb 08, 2016MVP
Hi Vinay85,
your observed behavior is most likely caused by an Source-IP Session Persistence profile.
When using such a persistence profile, then only the very first request of a given Source IP Address would become load balanced according to your selected load balancing algorythm. Subsequent request comming from the same Source-IP (aka. different client behind the same proxy), would then just stick to the same pool member.
If you need persistence for your application to work, you could experiment with the Cookie-Persistent profiles. In this case each individual client would become load balanced, but then stick to its initial node on subsequent requests (using an HTTP cookie)
Cheers, Kai