Loading...
Loading...
- Number of active connections is increasing over time. - Memory used by TMM increases over time. - Potential TMM restart is possible.
- Service may be impacted after a period. - TMM instances may restart.
This issue arises only when all the following conditions occur: - Hardware is chassis type. - There is more than one blade in service. - A fastL4 profile is configured (e.g., using bigproto). - SessionDB is used either by iRules or by native profile functionality.
None.
SessionDB-related accesses initiated via iRules are now properly cleaned up and no longer hang.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.