Bug ID 513646: APM(ACCESS)/SWG filter might process SessionDB replies after flow has been aborted resulting in orphaned timer

Last Modified: Oct 16, 2023

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5

Opened: Mar 20, 2015

Severity: 3-Major

Related Article: K37170914

Symptoms

APM(ACCESS)/SWG filter might process SessionDB replies after flow has been aborted resulting in orphaned timer.

Impact

This results in rare TMM crashes/cores. The backtrace from cores usually point to the timer.

Conditions

APM(ACCESS)/SWG.

Workaround

None

Fix Information

APM(ACCESS)/SWG filter operation no longer results in orphaned timers.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips