Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1
11.5.0, 11.4.1 HF2, 11.4.0 HF6
Opened: Oct 14, 2013
Related AskF5 Article: K15703
The access policy daemon (apd) shows high CPU usage and does not release it, in some rare conditions.
The impact is that the apd process might use 100% of the CPU and stop responding for incoming requests.
In rare cases, if the apd connection to the Kerberos key distribution center (KDC) was shutdown immediately after it was established, the Kerberos library might wait for the length of the initial message indefinitely, which causes one of apd threads to loop infinitely.
To work around this issue, restart the apd process.
Now, if the peer is shut down, Kerberos immediately terminates the connection.