-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor - P4
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.11.0
-
Component/s: Connection Management, Error Handling
-
Labels:None
MongoWaitQueueFullException is created with two messages:
- Too many threads are already waiting for a connection. Max number of threads (maxWaitQueueSize) of %d has been exceeded.
- Too many operations are already waiting for a server. Max number of operations (maxWaitQueueSize) of %d has been exceeded.
The exception message is the same regardless of the acquisition mode (synchronous/asynchronous). When using the e.g. Reactive Streams driver, one can easily assume that MongoDB creates up to %d threads.
I suggest aligning the wording towards "too many operations" to remove confusion about threads.