Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
11.5.0, 11.4.1 HF9
Opened: Sep 04, 2013
Related AskF5 Article: K14976
With connection queuing enabled, and with pool members having connection limit set, under certain race condition in the code, the pool members become unavailable and show that they have reached the connection limit. They stay in this state even after the connections themselves are long gone.
Pool members become unavailable, and remain unavailable.
Connection limit on pool members needs to be set. Queue connection needs to be set.
The pool now goes unavailable and comes back available.