RFR: 8288717: Add a means to close idle connections in HTTP/2 connection pool

Michael McMahon michaelm at openjdk.org
Tue Sep 27 14:46:26 UTC 2022


On Tue, 6 Sep 2022 13:56:15 GMT, Conor Cleary <ccleary at 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.

I'd agree 1200 sec (20 mins) is way too high. I would think 5-6 mins would be more appropriate.

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

PR: https://git.openjdk.org/jdk/pull/10183


More information about the net-dev mailing list