Bug ID 1002437: SSL Orchestrator configuration can become corrupt due to OutOfMemoryError

Last Modified: Jul 12, 2023

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

Opened: Mar 15, 2021

Severity: 3-Major

Symptoms

Restjavad can restart due to an OutOfMemoryError. If this occurs while SSL Orchestrator is in the process of deploying a change, it can lead to corruption of the configuration.

Impact

The configuration may fail to persist to MCP, and the shared iAppLX blocks used by SSL Orchestrator will can be set to error state.

Conditions

This can occur when the platform in use has insufficient memory with and has a relatively large number of configuration objects.

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

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips