Bug ID 559522: APM + FPS alerts dropped due to "APM HTTP Body too Big"

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
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, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,

Opened: Nov 23, 2015
Severity: 2-Critical


FPS alerts are sent by HTTP POST to a remote server, but if that POST body is too large, APM will reset the connection before the request reaches the remote server. The reset cause will be "APM HTTP Body too Big"


FPS + APM clientless mode will not work under the default APM configurations.


The combination of two conditions results in the dropped request: 1) One of the APM clientless modes is being used 2) The FPS alert request's body must be larger than the configured maximum request body size. The default is 64k


The maximum request body size is configurable through a DB variable: setdb tmm.access.maxrequestbodysize 128000

Fix Information


Behavior Change