RFR: 7116990: (spec) Socket.connect(addr,timeout) not clear if IOException because of TCP timeout [v3]

[Daniel Fuchs]

On Fri, 13 Jun 2025 15:20:47 GMT, Mark Sheppard <msheppar at openjdk.org> wrote:

>>> This is all that needs to be said. There is no need to state any typical values, but if you do then those values need to be factually correct, and for the currently supported platforms 60 seconds is not typical, it's 21, 75, and 128 seconds
>> 
>> The proposed wording in the current draft looks okay. It explains to the reader that establishing a TCP/IP connection is subject to an operating system timeout. It gives a sense of what that timeout might be, it's not hours or days, it's tens of seconds. I don't think we should attempt to list specific timeouts for specific operating system versions and configurations.
>
> why are you insisting on specifying 60 seconds? It does not exist on any supported OS platform. There is no need to specify any value in the apiNote, all it does is add misinformation

Maybe we could say:


The typical operating system timeout ranges within tens of seconds to minutes.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/25690#discussion_r2145436929