Bug ID 511196: UMU memory is not released when remote logger can't reach its detination

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6

Opened: Mar 08, 2015

Severity: 2-Critical

Symptoms

UMU memory is printed in the bd.log as being held although there is no traffic in the system.

Impact

Some memory is wasted and is not released for a long time

Conditions

Remote logger has an unreachable detination

Workaround

Fix the remote logger configuration, or the network issue

Fix Information

We fixed UMU memory slow releases that occurred when the remote logger's destination was unreachable.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips