[JAVA-2027] Connection pool does not properly open connections when ensuring minimum pool size Created: 04/Nov/15 Updated: 13/Jan/16 Resolved: 20/Nov/15 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management |
| Affects Version/s: | 3.1.0 |
| Fix Version/s: | 3.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
The connection pool ensures the minimum pool size in a background thread by creating an instance of InternalConnection. But the background thread does not call InternalConnection.open to actually force it to connect and authenticate. It should. |
| Comments |
| Comment by Jeffrey Yemin [ 07/Dec/15 ] |
|
The 3.2.0 driver, which contains a fix for this issue, has been released today. |
| Comment by Githook User [ 20/Nov/15 ] |
|
Author: {u'username': u'jyemin', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |