Bug ID 457293: Clustered Multiprocessing (CMP) peer connection is not removed in certain race conditions.

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10

Fixed In:
12.0.0, 11.5.2, 11.4.1 HF9

Opened: Apr 15, 2014
Severity: 3-Major
Related AskF5 Article:
K25058432

Symptoms

The CMP peer connection could be left there without being swept out when the connection at origin is aborted too soon in the connection flow.

Impact

Connections are leaked up to reaching a point when the memory is consumed.

Conditions

CMP with two tmm instances. Connection gets aborted.

Workaround

N/A

Fix Information

When the origin CMP instance couldn't find the connection after its peer replied, re-send a REMOVE message to the peer to remove it.

Behavior Change