[JAVA-4664] Clarify that socketTimeoutMS affects only reads Created: 28/Jun/22 Updated: 01/Jul/22 Resolved: 01/Jul/22 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | URI Options |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Valentin Kavalenka | Assignee: | Valentin Kavalenka |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Documentation Changes: | Not Needed | ||||||||
| Description |
|
socketTimeoutMS is documented incorrectly in ConnectionString. In actuality, this option is the same as SocketSettings.getReadTimeout. There is no way to directly control the write timeout in the Java SE (see |
| Comments |
| Comment by Githook User [ 29/Jun/22 ] |
|
Author: {'name': 'Valentin Kovalenko', 'email': 'valentin.kovalenko@mongodb.com', 'username': 'stIncMale'}Message: Clarify that `socketTimeoutMS` affects only reads (#975)
|