-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 3.3.0, 3.3.5
-
Component/s: None
-
Environment:Mongodb inside Docker
Driver connect from local Windows 10 machine
Steps to Reproduce:
1. Connect to a single server, with bufferMaxEntries=0
2. Stop the server
3. Query the server using db.collection().findOne, promise not resolve
4. Query the server using db.colllection().aggregate, promise got error, "MongoError:no connection available for operation and number of stored operation > 0"
5. Start the server
6. Query in step 3 above (findOne) got fires, and the promise is resolved with result
Is this the intended behaviour?