[JAVA-4160] Clarify whether maxPoolSize allows 0 option or no Created: 14/May/21  Updated: 28/Oct/23  Resolved: 01/Jul/21

Status: Closed
Project: Java Driver
Component/s: Configuration
Affects Version/s: None
Fix Version/s: 4.3.0

Type: Improvement Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Jeffrey Yemin
Resolution: Fixed Votes: 0
Labels: spec-compliance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
Related
related to JAVA-4216 DefaultConnectionPool and ConcurrentP... Closed
Documentation Changes: Not Needed

 Description   

DRIVERS Ticket Description
Script Target - If you can read this text, the script has failed


 Comments   
Comment by Githook User [ 01/Jul/21 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Add URI options spec tests for minPoolSize/maxPoolSize of 0

JAVA-4160
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/a2d3d1557f1330cdd62b9f91a2f403a07e51e616

Comment by Jeffrey Yemin [ 10/Jun/21 ]

Need to implement the new uri options spec tests.

Generated at Thu Feb 08 09:01:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.