Bug ID 755977: Missing check for NULL condition causes tmm crash.

Last Modified: Apr 11, 2023

Affected Product(s):
BIG-IP All(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,,,,,,,, 12.1.4,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3

Fixed In:
15.0.0,,, 12.1.5

Opened: Jan 18, 2019

Severity: 3-Major


Missing check for NULL condition causes tmm crash.


Traffic disrupted while tmm restarts.


This issue occurs when all of the following conditions are met: 1) The BIG-IP system receives a new connection request and attempts to select a pool member. 2) All pool members are unresponsive. This may be due to one of the following reasons: a) The pool members have reached their configured connection limit. b) There is no route to the pool members.



Fix Information

TMM correctly checks for NULL condition to prevent the crash.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips