Bug ID 668006: Suspended 'after' command leads to assertion if there are multiple pending events

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP All(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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.3.6

Opened: Jun 06, 2017
Severity: 3-Major
Related AskF5 Article:
K12015701

Symptoms

TMM crashes when an iRule has multi-parking commands including command after.

Impact

Traffic disrupted while tmm restarts.

Conditions

-- iRule has multi-parking commands. -- Command after is used multiple times in the iRule. Note: The exact condition of crashing tmm is not definitive, but when the above situation is met, it could trigger this crash.

Workaround

Depending on the iRule, (e.g., script that uses command after very heavily, very often), the usages can be combined: after 100 after 200 { some script } can be combined to after 300 { the script }

Fix Information

Suspended 'after' command no longer leads to assertion if there are multiple pending events

Behavior Change