[JAVA-3933] Async listCollections uses two connections Created: 13/Jan/21 Updated: 28/Oct/23 Resolved: 13/Jan/21 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Documentation Changes: | Not Needed |
| Description |
|
The method ListCollectionsOperation#executeAsync checks out two connections to execute the command, where only one is required. This creates unnecessary stress on the connection pool, and means that it will fail when maxPoolSize = 1. |
| Comments |
| Comment by Githook User [ 13/Jan/21 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Use single connection in async listCollections execution
|