[DIRAPI-217] Under heavy load, the Connection Pool will not provide valid connections

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.0-M27
• Fix Version/s: 1.0.0-M28
• Assignee: Unassigned
• Reporter: Emmanuel Lécharny
• Created: 07/Jan/15 10:23
• Updated: 08/Jan/15 16:53
• Resolved: 08/Jan/15 16:53

Description

What happens is that when a lot of threads are requesting connections from the pool, and if the number of idle connections get above the max idle connections configure for the pool, then some connections will be mandatory closed by the pool, and may remain in a transient state for a bit of time, and be allocated to a thread.

This is due to the fact we don't wait for the complete closure of a connection when we do a session.close(), which returns a CloseFuture.