Bug ID 700385: Behavioral Clarification For Tcl After Command

Last Modified: Jan 29, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4

Fixed In:
14.0.0

Opened: Jan 02, 2018
Severity: 2-Critical

Symptoms

Flows with after commands accrue in the TMM due to not-yet-executed after scripts, causing memory pressure.

Impact

Potential memory pressure, leading to out of memory and TMM failover. Traffic disrupted while tmm restarts.

Conditions

After command used in a Tcl script with a timeout beyond the connection lifetime.

Workaround

If the after command does not need to execute after the flow has been expired, use one of the *_CLOSED events to cancel the after command.

Fix Information

After commands on a closed or aborted flow will now be removed as soon as possible, rather than waiting for their timer to fire and detect they cannot be run, thereby significantly decreasing memory pressure.

Behavior Change