Fix bug with application of max idle time #176
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in #41, if concurrent actions have ensured that the pool has N connections (N > 1) and there are >=N single threaded actions using the pool before max idle time is reached then despite the fact that only 1 connection at a time has been used since the pool expanded to N no connections are timed out and released.
This was because a FIFO queue was used to gather checked-in connections which brought about round-robin behaviour. The fix is to switch to using a LIFO queue.