Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9
Opened: May 20, 2014
Related AskF5 Article: K16034
In addition to mappings used by successful connections, the Active Translation Mappings count incorrectly counts some pending translation mappings that ultimately are unused. These translation mappings are not active and should not be counted. Additionally, the Active Translation Mappings count is not decremented for these pending translation mappings when the mapping is recovered and made available for new connections.
Because of the miscounting, the Active Translation Mappings count tends to grow over time and become much larger than the connection count. The high count does not represent a memory leak or translation endpoints that are not available.
The high counts are associated with connection failures and can occur with heavy traffic or when there is a limited number of available translation endpoints.
The Active Translation Mappings now count only translation mappings that are actively in use.