Bug ID 456413: Persistence record marked expired though related connection is still active

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
11.2.0, 11.2.1, 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, 11.5.2, 11.5.2 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.3, 11.4.1 HF9

Opened: Apr 09, 2014
Severity: 3-Major
Related AskF5 Article:
K16070

Symptoms

A persistence record might be marked expired even though its corresponding connection is still active and passing traffic.

Impact

Persist records disappear in spite of flow activity that is more recent than the persist timeout.

Conditions

This occurs when using persistence.

Workaround

Set the timeout of persist to at least 33 seconds longer than the related flow timeout.

Fix Information

Persistence records are maintained when connection and persistence timeouts are with 33 seconds of each other.

Behavior Change