Bug ID 1117693: TMM restarts in loop when WAM applications attached to the default /common/webacceleration profile

Last Modified: Jun 28, 2025

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

Known Affected Versions:
16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2

Opened: Jun 21, 2022

Severity: 2-Critical

Symptoms

If the default /common/webacceleration profile is modified to have WAM applications attached, the internal APM apm-enduser-if-cache profile which is forced onto APM virtual servers will cause TMM to attempt to activate WAM - this fails with TMM in a recursive stack loop.

Impact

Traffic disrupted while tmm restarts.

Conditions

-- "/Common/webacceleration profile 'applications' field is populated.

Workaround

Don't put WAM applications on /Common/webacceleration on 16.x and above

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips