Load Balancing for new connections fails when jsessionid persistence profile is applied to VIP
Hi, We have applied jsessionid based persistence profile to the VIP to maintain active session persistence to same node. Also observed all new connections from different source ip's are getting to the same server instead of load balancing among pool members and later maintaining the session persistence. However with cookie persistence new connections are getting load balanced.
Below mentioned Configuration example.
virtual VS_X.X.X.X_https { snat automap pool Pool_APPServers destination X.X.X.X:https ip protocol tcp persist JSESSIONID_Persistence profiles { http_xforward {} oneconnect {} Client_CERT { clientside } tcp {} } } pool Pool_APPServers { monitor all http members { 1.2.3.4:8002 {} 1.2.3.4:8003 {} } }
Please let me know if my understanding related to jsessionid persistence for new connection is correct? or Any additional configuration is required to fix the issue.
Thanks, Rajendra