Last Modified: May 29, 2024
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5
Fixed In:
16.0.0, 15.1.1, 14.1.2.7, 12.1.5.2
Opened: Dec 06, 2019 Severity: 3-Major
When a large number of LTM objects are configured on BIG-IP, making updates via iControl REST can result in restjavad, restnoded, and/or icrd timeout errors.
REST operations can time out when they take too long, and it is not possible to increase the timeout.
Using iControl REST or an iApp to update a data-group that contains a large number of records, e.g., 75,000 or more.
N/A
ICRD/restjavad/restnoded timeouts are now configurable through sys db variables.
New Sys DB variables have been added to allow you to modify the timeout settings of restjavad, restnoded, and icrd: restnoded.timeout restjavad.timeout icrd.timeout The default value is 60 seconds for each of these. A restart of restjavad and restnoded is required for the change to take effect. tmsh restart /sys service restjavad tmsh restart /sys service restnoded