Bug ID 904373: MRF GenericMessage: Implement limit to message queues size

Last Modified: May 29, 2024

Affected Product(s):
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.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 16.0.0, 16.0.0.1

Fixed In:
16.1.0, 16.0.1, 15.1.0.5, 15.0.1.4, 14.1.3.1

Opened: Apr 27, 2020

Severity: 3-Major

Symptoms

The GenericMessage filter does not have a configurable limit to the number of messages that can be received.

Impact

If too many messages are queued, the system may exceed an internal count which could lead to a core.

Conditions

If a message is waiting for an asynchronous iRule operation during a GENERICMESSAGE_INGRESS or GENERICMESSAGE_EGRESS iRule event, new messages are placed in either the ingress or egress queue. As the number of messages increase, more memory is required.

Workaround

None.

Fix Information

The existing max_pending_messages attribute of the message router profile is used to limit the size of the queues.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips