Last Modified: May 29, 2023
Known Affected Versions:
220.127.116.11, 18.104.22.168, 15.1.8, 15.1.7, 15.1.7, 15.1.6, 22.214.171.124, 15.1.5, 126.96.36.199, 15.1.4, 188.8.131.52, 15.1.3, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.1.4
Opened: Feb 09, 2022 Severity: 3-Major
Restjavad restarts repeatedly when it has been configured to have a near maximal heap size by use of system database variables restjavad.useextramb and provision.extramb
Restjavad restarts and REST API may be unavailable.
Affected versions have fix for ID 776393 ( https://cdn.f5.com/product/bugtracker/ID776393.html ) Affected version do not have fix for ID 943653 ( https://cdn.f5.com/product/bugtracker/ID943653.html ) Value of sys db restjavad.useextramb is true. Value of sys db provision.extramb is higher than approximately 2450MB (possibly could have issue from slightly lower values but above 2260MB and below will be safe) Systems with higher numbers of CPU cores (8 and above) are more likely to be affected
For software versions that have provision.restjavad.extramb, introduced by ID 1025261 (from 18.104.22.168, 15.1.7) just reduce that to a value of 2192 MB or lower, and restart restjavad. This should affect only access to REST API for a few seconds. For software versions before that lower sys db provision.extramb to a value of 2260 MB. tmsh modify sys db provision.extramb value 2260 Note this is service affecting, and will need to be carried out in turn on each member of a device service cluster Note this is likely to reduce host memory available which if left too low will increase likelihood of system issues. If in any doubt use a fixed version.
Restjavad no longer restarts with higher values of sys db provision.extramb