[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:
Related
related to JAVA-4148 Enable TCP_USER_TIMEOUT by default wh... Closed
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 JAVA-4148 for more details), which is why in the driver socketTimeoutMS does not affect writes.



 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)

JAVA-4664
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/a14bb7e77464a17a5323ba8c8ca37551b689993d

Generated at Thu Feb 08 09:02:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.