Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP All
Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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: May 08, 2014
Severity: 3-Major
Related Article:
K58224211
Asynchronous commands fail silently when used in ACCESS_SESSION_CLOSED events in iRules.
When asynchronous commands are used in ACCESS_SESSION_CLOSED, they fail silently. When asynchronous commands are used, the outcome is unpredictable. If the asynchronous command returns synchronously, the system operates as expected. In all other cases, the operation fails and no error is reported. The probability of failure increases with the number of TMMs.
Asynchronous commands used in ACCESS_SESSION_CLOSED events in iRules. Typically, using ACCESS_SESSION_CLOSED occurs during session expire or an explicit logout. In such cases, no flow is attached to the event. As a result, if an asynchronous command is used in this event, there is no flow to park on.
Do not use asynchronous commands in ACCESS_SESSION_CLOSED.
The system now logs an error when an asynchronous command runs in ACCESS_SESSION_CLOSED events in iRules. This is correct behavior.
