Bug ID 776393: Restjavad restarts frequently due to insufficient memory with relatively large configurations

Last Modified: May 03, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
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, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 16.0.0, 16.0.0.1, 16.0.1

Fixed In:
16.0.1.1, 15.1.3, 14.1.4

Opened: Apr 25, 2019
Severity: 2-Critical

Symptoms

Restjavad restarts frequently -- approximately every 5 minutes -- due to the JVM heap running out of memory

Impact

REST API intermittently unavailable.

Conditions

-- BIG-IP system with no extra memory given to restjavad. -- The configuration contains a large number of configuration items related to APM access-policies, APM policy-items, APM policy agents, LTM nodes, LTM rules, DNS Requests, sys application services, LTM data-groups, LTM profiles, security bot-defense profiles, and sys file ssl-certs.

Workaround

Give restjavad extra memory, using the following commands. The example below allocates 2 GB of extra memory to restjavad: tmsh modify sys db restjavad.useextramb value true tmsh modify sys db provision.extramb value 2000 bigstart restart restjavad To persist the change above with system reboots, save the configuration with: tmsh save sys config

Fix Information

Default restjavad heap memory has been increased to 384MB

Behavior Change