Last Modified: Nov 22, 2021
See more info
Known Affected Versions:
Opened: Feb 26, 2020
TMM leaks memory and eventually crashes when it cannot allocate any more memory.
The leak initially causes traffic disruption, as TMM reaps flows prematurely in an effort to free up memory. Eventually, TMM crashes, as it is unable to allocate any more memory. When this happens, redundant systems fail over. Traffic disrupted while tmm restarts.
The 'ACCESS::session remove' iRule command is called in an event other than an ACCESS event (for example, the CLIENTSSL_HANDSHAKE event). The only affected versions are 184.108.40.206 and 220.127.116.11.
Do not use the 'ACCESS::session remove' iRule command under any event that isn't an ACCESS event. To restore TMM to a fully functional state after making all necessary configuration changes, or to temporarily work around this issue, you can restart TMM with the following command: bigstart restart tmm