Last Modified: Jan 17, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1
Opened: Mar 24, 2022 Severity: 4-Minor
Observe the logs in /var/log/daemon.log Nov 8 01:13:27 localhost.localdomain emerg logger[6270]: Re-starting restjavad Java core generated in folder /var/core.
Restjavad will be restarted.
1. Provision ASM 2. Huge number of requests to restjavad 3. cpu is hitting 100%
More heap memory can reduce cpu consuming operations, fewer GC cycles, less frequent minor GCs, overall less overhead for memory management can add for less cpu usage. Please increase the value of provision.extramb and provision.restjavad.extramb by 200MB at a time ( 400, 600, 800 ...) till the issue resolves. Since changing the value of provision.extramb is service affecting you may want to start with a higher value so there is more room to experiment to find a good value for restjavad heap size. Note 500MB is equivalent to large management provisioning and 200MB is the same as medium management provisioning. NB provision.extramb value doesn't sync between peers (by design) and must be changed on each peer, one at a time, and is service affecting when changed on active. On ASM provisioned system it can take approximately 15 minutes for system to reprovision. tmsh modify sys db provision.extramb value 200 ( 400, 600, 800 ...) tmsh modify sys db provision.restjavad.extramb value 600 (800, 1000, 1200 ... bigstart restart restjavad Increase timeout # tmsh modify sys db icrd.timeout value 300 # tmsh modify sys db restjavad.timeout value 300 # tmsh modify sys db restnoded.timeout value 300 bigstart restart restjavad restnoded
None