Bug ID 669459: Efect of bad connection handle between APMD and memcachd

Last Modified: Nov 07, 2022

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,

Fixed In:

Opened: Jun 15, 2017

Severity: 3-Major


When a connection handle (fd) between apmd and memcachd gets bad (someone else is using or already closed by memcachd), all worker threads gets locked out. A cleaner thread then restart APMD with an assert.


APMD gets locked down , eventually restart with a core.


This is difficult to reproduce. It happens if one or more connection handle between apmd worker thread and memcachd gets misused.



Fix Information

Communication between APMD and TMM has been improved to be more tolerant of error conditions.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips