Bug ID 714902: Restjavad may hang if discover task fails and the interval is 0

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1

Fixed In:
14.1.0, 14.0.0

Opened: Apr 12, 2018

Severity: 3-Major

Symptoms

If a discover task fails because of a network issue, the system tries to run the task again at the next scheduled time. If the discover interval is set to 0, the system retries immediately, which may cause restjavad hang.

Impact

The discover task tries to use a lot CPU when restjavad continuously retries the task.

Conditions

If a provider has configured discover interval 0 and the discover task failed because of network issues.

Workaround

Change the discover interval to 1 hour or more.

Fix Information

Now, if the discover interval is 0 and the discover task fails because of a network issue, the system sends the task to the finished state and does not retry anymore.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips