[JAVA-2825] Timeout while receiving message with Mongo Connection pooling using java Created: 03/Apr/18 Updated: 27/Oct/23 Resolved: 03/Apr/18 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management |
| Affects Version/s: | 3.2.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Narasimha Reddy | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux |
||
| Attachments: |
|
| Description |
|
Production we are connecting with Mongo DB using java (connection Pooling) driver 3.2.2. every day We are getting almost 300 requests below error (MongoSocketReadTimeoutException) it is just coming 1 minute (or) 1.30 minute . after this come again system working fine . could you please tell me why it is getting failed |
| Comments |
| Comment by Jeffrey Yemin [ 03/Apr/18 ] |
|
Just to let you know the JAVA project is for reporting bugs and feature requests with the Java driver. In general the best place to ask questions using the Java driver or MongoDB in general is either the mongodb-user Google Group or Stack Overflow as public discussion there can help others learn and resolve similar issues. To get you started, I can tell you that generally a MongoSocketReadTimeoutException indicates either a network issue or a slow response from the MongoDB server for the operation that's timing out. It's not an issue with the driver itself. You might try examining the server logs or adding tracing to your Java application to determine what the pattern is for the operations that are timing out. The driver has extensive logging and monitoring functionality that may help you. See the reference documentation for further information |