On Tue, 6 Sep 2022 13:56:15 GMT, Conor Cleary <ccle...@openjdk.org> 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. It seems that the overall preference is to make use of the already existing `jdk.httpclient.keepalive.timeout` property. I'll soon push a set of changes which reflects this. Another change I will include will be to do with reducing the default 1200ms value for the `jdk.httpclient.keepalive.timeout` as discussed above. ------------- PR: https://git.openjdk.org/jdk/pull/10183
