Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1
11.5.0, 11.4.1 HF2, 11.4.0 HF6, 11.3.0 HF9, 11.2.1 HF11
Opened: Sep 04, 2013
Related AskF5 Article: K15704
When using Session Initiation Protocol (SIP) and Message-based Load Balancing (MBLB) and TCP/TLS you may encounter memory issues, due to ineffective flow control. When remote client/server drains much slower than the rate of messages queued for them, the pending messages could use more memory than necessary.
TMM could get into aggressive memory sweeper, often
SIP configured in a MBLB profile.
Increase the count of server-side connections to distribute messages.
The mblb profile's egress settings could control the egress pending Q size and prevents it from growing to a size that impacts performance of other connections.