On Thu, 3 Nov 2022 16:28:08 GMT, Conor Cleary <[email protected]> wrote:
>> **Issue**
>> When using HTTP/2 with the HttpClient, it can often be necessary to close an
>> idle Http2 Connection before a server sends a GOAWAY frame. For example, a
>> server or cloud based tool could close a TCP connection silently when it is
>> idle for too long resulting in ConnectionResetException being thrown by the
>> HttpClient.
>>
>> **Proposed Solution**
>> A new system property, `jdk.httpclient.idleConnectionTimeout`, was added and
>> is used to specify in Milliseconds how long an idle connection (idle
>> connections are those which have no currently active streams) for the
>> HttpClient before the connection is closed.
>
> Conor Cleary has updated the pull request incrementally with one additional
> commit since the last revision:
>
> 8288717: IdleConnectionTimeout can use Keep Alive or Custom Value
src/java.net.http/share/classes/jdk/internal/net/http/ConnectionPool.java line
55:
> 53: final class ConnectionPool {
> 54:
> 55: static final long KEEP_ALIVE = KEEP_ALIVE_TIMEOUT; // seconds
I'd suggest removing line 55 and change the references below to
KEEP_ALIVE_TIMEOUT
-------------
PR: https://git.openjdk.org/jdk/pull/10183
