Bug ID 460076: Deletion of XML profiles from Enforcer memory

Last Modified: Mar 17, 2021

Bug Tracker

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

Known Affected Versions:
11.3.0, 11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0

Opened: May 01, 2014
Severity: 3-Major

Symptoms

XML profiles may not get deleted from the Enforcer's memory once they are deleted from the configuration. This might lead ASM to run out of memory for XML and JSON processing, recognizable by the error message "XML is running out of memory".

Impact

May lead to out of memory within the Enforcer application. (BD)

Conditions

Deletion of XML profiles configuration.

Workaround

There are two workarounds: 1) Add a custom provisioning table to increase the host and ASM memory allocation by 1Gb. 2) Set the value of the parameter "total_xml_memory" to around 2Gb by typing the following command from the command line: /usr/share/ts/bin/add_del_internal add total_xml_memory 2000000000

Fix Information

XML profiles are now deleted from the Enforcer's memory once they are deleted from the configuration. This was done to prevent ASM from running out of memory for XML and JSON processing.

Behavior Change