Symptoms

Some authentication requests never complete. APMD responsiveness degrades over time and eventually restarts.

Impact

APMD responsiveness degrades over time, usually weeks, before eventually restarting.

Conditions

The CRL Authentication server must be alive enough to accept connections but busy enough to drop requests without closing connections.

Workaround

Restarting the CRL Authentication server usually releases the waiting threads and restores APMD responsiveness.
Using a BIG-IP monitor for the CRL backend can detect the issue and allow recovery before the need for APMD to restart.

Fix Information

CRL agent now times out and returns an error when the CRL server becomes unresponsive.

Behavior Change

The CRL Authentication agent now times out and returns an error instead of waiting forever. In previous releases, if enough threads were waiting, APMD performance degraded and eventually restarted.