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

Last Modified: Jan 23, 2020

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 15.0.0, 15.0.1, 15.0.1.1, 15.1.0

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

None

Behavior Change