Bug ID 548866: Tomcat might become unresponsive when the UI throws an Out of Memory Exception

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:

Opened: Sep 28, 2015

Severity: 3-Major

Related Article: K25554628


The UI might runs out of memory on a page that is memory heavy, such as on the Network Map page of a configuration with many Virtual Servers, Pools, iRules, Pool Members/Address Nodes, and the Tomcat UI server might become unresponsive.


The UI becomes unresponsive.


Using the Network Map page to render the map with a large number of components and multiple consecutive users can cause the UI to run out of memory.


Use the search filter to reduce the result set. When the UI becomes unresponsive, restart Tomcat. Also, consider increasing the memory allocation for Tomcat.

Fix Information

When Tomcat runs out of memory and becomes unresponsive, it will restart itself automatically.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips