F5 | 1012513

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 ... -- 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 s...