Bug ID 944441: BD_XML logs memory usage at TS_DEBUG level

Last Modified: Sep 13, 2023

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

Known Affected Versions:
13.1.3,,,,,,, 13.1.4,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 16.0.0,, 16.0.1,

Fixed In:
16.1.0,, 15.1.4,, 13.1.5

Opened: Sep 13, 2020

Severity: 4-Minor


There are two messages in BD_XML logs that the system reports at the TS_DEBUG log level, but they should be logged as TS_INFO. BD_XML|DEBUG |Sep 10 14:51:19.335|1456|xml_validation.cpp:1687|after create of profile 754. (xml memory 5111702493 bytes) BD_XML|DEBUG |Sep 10 14:51:19.335|1456|xml_validation.cpp:1586|add profile 755. name: /ws/replanifierIntervention_V1-0 is soap? 1 (xml memory before add 5111702493 bytes)


Messages that should be logged at the TS_INFO level are logged at the TS_DEBUG level. These are informational log messages.


These messages can occur when XML/JSON profiles are configured.



Fix Information

The relevant two BD_XML logs are now categorized as TS_INFO.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips