|
Hi nsryn, this stack trace does not indicate a bug in the driver. It merely indicates that the driver timed out while reading a response from a MongoDB server. This could indicate a number of possible issues, including (but not limited to):
- a slow operation in the server (e.g., a query requiring a collection scan) that exceeds the configured socket read timeout.
- an issue at the networking layer which prevented the driver from reading the response from the socket before the configured socket read timeout.
As such, I've changed the issue type to Question and am closing it.
Just to let you know this project is for Java driver bugs or feature requests. The best place for questions regarding MongoDB usage or the Java driver specifics is the mongodb-user mailinglist or stackoverflow as you will reach a broader audience there. If your business requires an answer from MongoDB within a time frame then we do offer production support.
If you do follow up via one of the options above please post a link and someone will follow the conversation there.
|