Bug ID 859113: Using "reject" iRules command inside "after" may causes core

Last Modified: Sep 13, 2023

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

Known Affected Versions:
14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1

Fixed In:
16.0.0, 15.1.0.2, 14.1.2.5

Opened: Dec 11, 2019

Severity: 4-Minor

Symptoms

In iRules, when "reject" is used inside "after -periodic" and it is followed by "GENERICMESSAGE::message create". It may trigger a tmm core. Below is an example iRule. when CLIENT_ACCEPTED { ... omitted ... after 1000 -periodic { ... omitted ... reject GENERICMESSAGE::message create "test" } } This relates to ID 859721

Impact

Traffic disrupted while tmm restarts.

Conditions

- "reject" is used inside "after -periodic" - it is followed by "GENERICMESSAGE::message create"

Workaround

There are 2 possible work-arounds - use "return" command after "reject" to exit after script immediately after "reject" command is invoked - add routine to cancel the after in CLIENT_CLOSED event

Fix Information

Using "reject" iRules command inside "after" no longer cause core.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips