Bug ID 1089625: Java core dump with SIGABRT while high cpu load in BIG-IP

Last Modified: Oct 07, 2024

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

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, 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

Opened: Mar 24, 2022

Severity: 4-Minor

Symptoms

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.

Impact

Restjavad will be restarted.

Conditions

1. Provision ASM 2. Huge number of requests to restjavad 3. cpu is hitting 100%

Workaround

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 +200 ( 400, 600, 800......) till the issue resolves. tmsh modify sys db provision.extramb value 200 ( 400, 600, 800......) tmsh modify sys db provision.restjavad.extramb value 584 (784, 984, 1184......) bigstart restart restjavad tmsh save sys config 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

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips