HTTP requests carrying the same application cookie value may be incorrectly routed to different backend pool members disrupting the user traffic
search cancel

HTTP requests carrying the same application cookie value may be incorrectly routed to different backend pool members disrupting the user traffic

book

Article ID: 398013

calendar_today

Updated On:

Products

VMware Avi Load Balancer

Issue/Introduction

 

  • Multiple requests with identical app cookie values are routed to different pool members.

  • Session stickiness is not maintained.

  • Application behavior appears inconsistent or broken during user sessions.

 

 

Cause

This issue occurs when Connection Multiplexing is disabled in the Virtual Service (VS) Application Profile. When multiplexing is turned off, the connection persistence behavior relies solely on the existing TCP connections between the Service Engine (SE) and pool members. If cookie-based persistence is used without multiplexing, requests may get routed incorrectly.

Resolution

Enable Connection Multiplexing in the Application Profile of the affected Virtual Service.

Steps:

  1. Navigate to:
    Templates → Profiles -> Application

  2. Edit the App Profile used by the Virtual Service.

  3. Locate and enable the Connection Multiplexing setting.

  4. Save the profile and apply the changes.



Recommended Practice

  • Always enable connection multiplexing when using cookie persistence.

  • Multiplexing allows new HTTP requests to be routed independently of previous TCP connections, ensuring persistence logic works as intended.

Refer for more details:: https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/30-2/vmware-avi-load-balancer-configuration-guide/load-balancing-overview/application-profile/connection-multiplexing.html

 

Powered by Wolken Software