Hi,
It’s been a while since you posted this question. Have you found out what’s happening yet?
The AssertionException
message you observed could be caused by intermittent issues on the network layer, or the application closes its connection to the database before MongoDB has a chance to respond (e.g. due to the query exceeding a timeout).
Note that the connectTimeoutMS
setting does not regulate per-query timeout. To paraphrase from the linked page, the setting governs “The time in milliseconds to attempt a connection before timing out”.
If you’re still having this issue, could you post:
AssertionException
messagesPlease also ensure that your MongoDB deployment follows the recommended settings outlined in the Production Notes to ensure that MongoDB runs with the optimal settings.
Best regards,
Kevin
Hi Avinash, Abishek
Interestingly it gives this error with different port numbers in the end
I believe it’s the source port of the connection. See TCP/IP Port for a brief description.
The error you described could be caused by many things, such as network issues, the application trying to open too many connections to the server, or misconfigured server.
Please open a new thread, and post a short & simple version of your source code that can reproduce the error you’re seeing, along with your MongoDB version, your driver version, your deployment details (topology, hardware spec, etc.), any extra mongod
parameters and config files, and what you have tried so far.
Best regards
Kevin