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

[Mark Sheppard]

On Fri, 13 Jun 2025 13:49:55 GMT, Jaikiran Pai <jpai at openjdk.org> wrote:

>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".

Right, the objective is to convey to a developer that when specifying a timeout to the connect method, that this timeout may be superseded by an OS's TCP/IP configuration's Connect timeout settings.

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

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

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