-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.5.9
-
Component/s: Change Streams
Hi,
The event 'error' is not called when the client is not allowed to connect by mongod. This happens when mongodb configuration file setting set maxIncomingConnections to eg. 7, but more than 7 clients try to connect to listen to the changes with change streams. The driver keep trying to reconnect the refused client and no error event is triggered.
The error event should be triggered so the developer can be alarmed and decide how to handle the logic.