[JAVA-5298] Adjust setSoTimeout to apply to aggregate read Time Created: 23/Jan/24 Updated: 07/Feb/24 Resolved: 07/Feb/24 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Slav Babanin | Assignee: | Ross Lawley |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Client Side Operations Timeout |
| Quarter: | FY24Q3 |
| Assigned Teams: |
Java Drivers
|
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
| Description |
|
The read method in SocketStream sets the socket timeout (setSoTimeout) only once at the beginning, leading to a refresh of the timeout for each new read. Expected Behavior: The aggregate of all reads to receive a server response should be under a single timeout, as per MongoDB's client-side operations timeout specifications. Acceptance criteria:
Performance Impact: To be determined. |