[JAVA-3215] Connection pool should prune stale connections before ensuring minimum pool size Created: 25/Feb/19 Updated: 28/Oct/23 Resolved: 04/Mar/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management |
| Affects Version/s: | None |
| Fix Version/s: | 3.11.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Currently, the connection pool's background task only tries to prune connections before ensuring minimum pool size if either maxIdleTime or maxLifeTime is specified. It should also check whether there are possibly any stale connections in the pool. |
| Comments |
| Comment by Githook User [ 04/Mar/19 ] |
|
Author: {'name': 'Jeff Yemin', 'username': 'jyemin', 'email': 'jeff.yemin@10gen.com'}Message: Prune connections in background task if generation has changed
|
| Comment by Jeffrey Yemin [ 25/Feb/19 ] |
|
I have a local branch with a fix for this, but it needs a test. |