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

[Jaikiran Pai]

On Fri, 13 Jun 2025 09:16:39 GMT, Mark Sheppard <msheppar at openjdk.org> wrote:

> Also first sentence need minor refinement changing connection timeout to connect timeout
>
> connection timeout is when the connection is established

I haven't previously seen connection timeout term being used to mean a timeout (for the connection?) after the connection has been established. I'll however change that text to say "connect timeout" shortly.

> I don't understand why you are persisting with 60 seconds, when the original reporter shows its a default of 21 seconds on Windows, which I have also confirmed and that windows requires. 21 seconds is a very much not typically 60 seconds

The timeout values noted in that text are mere examples to convey the detail that application developers need to be aware that the `timeout` they pass to the `connect()` method may not influence connection establishment failure due to timeout. They aren't exhaustive. I had considered including 21 in that text too. Alan's suggestion was to mention "60 or 75 seconds".

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

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