Last Modified: May 14, 2019
See more info
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: Jun 27, 2017
Some authentication requests never completes. APMD responsiveness degrade over time and eventually restart.
APMD responsiveness degrades over time, usually weeks, before eventually restarting.
The HTTP Authentication server must be alive enough to accept HTTP connections but busy enough to drop requests without closing connections.
Restarting the HTTP Authentication server usually releases the waiting threads and restores APMD responsiveness. Using a BIG-IP monitor for the HTTP backend can detect the issue and allow recovery before the need for APMD to restart.
HTTP agent now times out and returns an error when the HTTP server becomes unresponsive. This allows recovery without restarts.
The HTTP Authentication agent will time out and return an error instead of waiting forever. If enough threads were waiting, APMD performance degraded and eventually restarted.