Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.4.1, 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:
13.0.0
Opened: Feb 19, 2016 Severity: 4-Minor
'ACCESS::session exists' returns TCL error if there is no APM session associated with connflow
Uncaught TCL errors result in connection termination and RST being sent to client or backend. Functionality that uses iRules with 'ACCESS::session exists' may be impacted.
There is no APM session associated with connflow
Internal F5 iRules do not have workaround. Customer iRules can be modified to run 'ACCESS::session exists' inside catch {}. This will not lead to connection termination / RST.
'ACCESS::session exists' now returns false instead of TCL error when there is no APM session associated with connflow.