Bug ID 643547: APMD initialization may fail when large number of access policy agents are configured in access policies installed on BIG-IP

Last Modified: Oct 06, 2020

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, 13.0.0

Fixed In:
13.1.0, 13.0.0 HF1, 12.1.2 HF1

Opened: Feb 06, 2017
Severity: 3-Major
Related AskF5 Article:


Requests to /my.policy are not getting HTTP responses. Log file '/var/log/apm' contains large number of error messages about failed XML data creation: err apmd[5076]: 01490207:3: SAML Agent XML thread specific data creation error: ERR_FAIL.


APMD will not able to process any requests.


This issue occurs when all of the following conditions are met: -- Your BIG-IP APM system is configured with a large number of access policy agents. -- You are performing an operation that requires the apmd process to start. -- For example, your BIG-IP APM system is reloaded, you install a new image, or you manually restart the apmd process.


For some configurations and platforms, you can use the following steps to recover: - Remove all unused access policies (if applicable). - Restart apmd.

Fix Information

Now APMD initialization will no longer fail at XML initialization when a large number of access policies/agents are present in the configuration.

Behavior Change