Load Balancing Not Happening for Pool Members of a Performance Layer VIP

A OneConnect profile works with the HTTP profile, and when there is an HTTP Request/Response, it detaches the server-side connection from the client-side connection. Then, when the client makes a new HTTP Request, there is a new load-balancing decision for a pool member. If a pool member is selected that already has a server-side connection, that connection is reused, otherwise a new server-side connection is created.

This is not only more efficient, but is ensures that each HTTP Request has a load-balancing decision - without the One-Connect profile (or an irule that does a LB::detach on HTTP_RESPONSE) then there will still only be a load-balancing decision on the first request.