Bug ID 1644333: TMM fails to reconnect to redis after current connection fails following five retries

Last Modified: Nov 29, 2025

Affected Product(s):
BIG_IP_NEXT(CNF) CNF(all modules)

Fixed In:
1.4.0

Opened: Sep 09, 2024

Severity: 2-Critical

Symptoms

When a connection to Redis is lost, TMM attempts to reconnect with up to five retries. If all retries fail, TMM gives up and will only retry upon receiving session requests.

Impact

In the current implementation, if TMM's connection to Redis fails, it only attempts to reconnect when a new Session DB API call is made. Ideally, TMM should reconnect to Redis immediately, so Session DB callbacks (such as when Redis deletes an entry due to a timeout) can be handled correctly by TMM.

Conditions

1. Bring down the DSSM. 2. TMM attempts to connect to Redis with up to five retries. 3. If the connection fails, TMM gives up and will only retry when there is a session request at TMM.

Workaround

None

Fix Information

The MAX retry condition has been removed. With this fix, TMM will continuously retry to connect to Redis.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips