Bug ID 859721: Using GENERICMESSAGE create together with reject inside periodic after may cause core

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 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 "GENERICMESSAGE::message create" is called after "reject" command inside "after -periodic", it may cause core. Below is an example iRules. when CLIENT_ACCEPTED { ... omitted ... after 1000 -periodic { ... omitted ... reject GENERICMESSAGE::message create "test" } } This relates to ID 859113.

Impact

Traffic disrupted while tmm restarts.

Conditions

"GENERICMESSAGE::message create" is called after "reject" inside "after -periodic"

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 GENERICMESSAGE create together with reject inside periodic after no longer cause core

Behavior Change