[JAVA-3607] MongoDB random exception Created: 27/Jan/20 Updated: 27/Oct/23 Resolved: 24/Feb/20 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Reactive Streams |
| Affects Version/s: | 3.10.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dzmitry Chaulytka | Assignee: | Ross Lawley |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ibm cloud |
||
| Description |
|
We are using MongoDB v4.2 on IBM Cloud over the Reactive MongoDB Driver v1.11. We are currently experiencing the following exception randomly, usually after some period of the app inactivity:
or
From what I've read and from what the JavaDoc gives for the driver - keepAlive parameter is supposed to be set to true by default. But to be on the safe side - we are setting it explicitly:
But that does not seem to solve the issue. It occurs randomly and rarely |
| Comments |
| Comment by Raman Gupta [ 14/Aug/22 ] |
|
Same problem here. I use Atlas as my server and don't have access to the server logs. |
| Comment by Ross Lawley [ 29/Jan/20 ] |
|
Thanks for the ticket, both errors reported happen at a low level within the Java networking layer: Caused by: java.io.IOException: Broken pipe & Caused by: java.io.IOException: Connection reset by peer. This indicates that the connection to the server was broken. Do you have any network information / server logs for that time? Perhaps they can shed a light on why the connection was reset / broken. Kind Regards, Ross |