Bug ID 488416: Connection pooling and iSession profiles are not exclusive

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP AAM(all modules)

Fixed In:
12.0.0

Opened: Nov 03, 2014
Severity: 3-Major

Symptoms

Connection pooling (e.g., OneConnect) profiles and iSession profiles both configure connection pooling, so they should be mutually exclusive.

Impact

Having both configured might interfere with iSession tunnel re-use and cause more resources to be consumed by iSession tunnels that remain open instead of being put in the iSession pool.

Conditions

Configurations with both a connection pooling profile and an iSession profile with a virtual server.

Workaround

Modify virtual server configurations to have either a connection pooling profile or an iSession profile, but not both.

Fix Information

Connection pooling profiles and iSession profiles are now exclusive. Connection pooling for iSession tunnels is controlled by the connection reuse iSession profile attribute.

Behavior Change

Connection pooling profiles and iSession profiles are now exclusive. Connection pooling (e.g., OneConnect) profiles and iSession profiles both configure connection pooling. Beginning in this release, they have been made mutually exclusive. Connection pooling for iSession tunnels is controlled by the connection reuse iSession profile attribute. Note: Configurations with both a connection pooling profile and an iSession profile with a virtual server should be corrected before installing releases containing this profile exclusion.