Bug ID 626542: Unable to set maxMessageBodySize in iControl REST after upgrade

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, TMOS(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2

Fixed In:
13.0.0, 12.1.2 HF1

Opened: Nov 02, 2016
Severity: 3-Major
Related AskF5 Article:
K86935473

Symptoms

After upgrading and attempting to set maxMessageBodySize via iControl REST, you get an error indicating the command is not implemented: {"code":400,"message":"onPut Not implemented","originalRequestBody":"{\"maxMessageBodySize\": \"111111111\"}","referer":"127.0.0.1","restOperationId":216941,"kind":":resterrorresponse"}

Impact

Command fails, unable to set maxMessageBodySize.

Conditions

This occurs when upgrading from v11.6.1 to v12.1.0, v12.1.1,or v12.1.2, and applying the UCS from the 11.6.1 release. The error is generated because new defaults were added but they are not set on UCS restore.

Workaround

If you encounter this after an upgrade and UCS restore, you can run the following commands from the BIG-IP command line: 1. curl -X DELETE http://localhost:8100/shared/storage?key=shared/server/messaging/settings/8100. 2. bigstart restart restjavad.

Fix Information

You can now set maxMessageBodySize via iControl REST after upgrading.

Behavior Change