Bug ID 1012513: Restjavad memory leak when the BIG-IP Dashboard is used/accessed actively

Last Modified: May 02, 2024

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

Known Affected Versions:
13.1.5, 13.1.5.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4

Opened: Apr 19, 2021

Severity: 3-Major

Symptoms

-- Restjavad may become unstable if the amount of memory required by the daemon exceeds the value allocated for its use. -- Restjavad might restart frequently due to the JVM heap running out of memory.

Impact

Memory leaks/out-of-memory errors might cause iControlRest API intermittently unavailable.

Conditions

-- BIG-IP system with no extra memory given to restjavad. -- The configuration contains a large number of configuration items w.r.t to APM, LTM, security(ASM), and SSL Orchestrator. -- The memory required by the restjavad daemon may grow significantly in system configurations with either a high volume of device statistics collection (AVR provisioning) or a relatively large number of LTM objects managed by the REST framework.

Workaround

-- Limit the active use of the DashBoard and restart java (bigstart restart restjavad) when the memory levels peak. OR -- Increase the memory allocated for the restjavad daemon (e.g., 2 GB), by running the following commands in a BIG-IP terminal. tmsh modify sys db restjavad.useextramb value true tmsh modify sys db provision.extramb value 2048 bigstart restart restjavad Note: This may lead to an impact on multi-module systems with ASM as approximately only 50-60% of provision.extramb value would be allocated as extra host memory and restjavad may take up to 80% of provision.extramb. It also lowers the ASM-specific host allocation resulting in some tighter memory constraints on ASM daemons. Try to use the smallest value that works.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips