Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP AAM
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
12.0.0
Opened: Nov 03, 2014 Severity: 3-Major
Connection pooling (e.g., OneConnect) profiles and iSession profiles both configure connection pooling, so they should be mutually exclusive.
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.
Configurations with both a connection pooling profile and an iSession profile with a virtual server.
Modify virtual server configurations to have either a connection pooling profile or an iSession profile, but not both.
Connection pooling profiles and iSession profiles are now exclusive. Connection pooling for iSession tunnels is controlled by the connection reuse iSession profile attribute.
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.