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

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,

Fixed In:

Opened: Dec 11, 2019
Severity: 4-Minor


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


Traffic disrupted while tmm restarts.


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


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