Paul Scholz created MRESOLVER-584:
-------------------------------------
Summary: JDK transport: HTTP2 GOAWAY handling
Key: MRESOLVER-584
URL: https://issues.apache.org/jira/browse/MRESOLVER-584
Project: Maven Resolver
Issue Type: Bug
Components: Resolver
Affects Versions: 2.0.0-alpha-11, 2.0.0-alpha-10, 2.0.0-alpha-9, 2.0.0,
2.0.0-alpha-8, 2.0.0-alpha-7, 2.0.0-alpha-6, 2.0.0-alpha-5, 2.0.0-alpha-4,
2.0.0-alpha-3, 2.0.0-alpha-2
Reporter: Paul Scholz
Attachments: exception.log
I am encountering a problem with the implementation of JDK transport using
HTTP/2, specifically related to re-establishing connections after receiving a
GOAWAY frame. (RFC quote below)
Just for example a nginx server with default configuration does only allow 1000
requests per connection before requiring "establishing a new connection".
This results in IOException, stopping resolution process: [^exception.log].
Related to: [How to handle HTTP/2 GOAWAY with
java.net.HttpClient?|https://stackoverflow.com/a/55092354]
{quote}Sets the maximum number of requests (...) that can be served through one
HTTP/2 connection, after which the next client request will lead to connection
closing and the need of establishing a new connection.
--
[https://nginx.org/en/docs/http/ngx_http_v2_module.html#http2_max_requests|http://nginx.org/en/docs/http/ngx_http_v2_module.html#http2_max_requests]
[--
https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_requests|https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_requests]
{quote}
{quote}Once sent, the sender will ignore frames sent on streams initiated by
the receiver if the stream has an identifier higher than the included last
stream identifier. Receivers of a GOAWAY frame MUST NOT open additional streams
on the connection, although a new connection can be established for new streams.
-- [RFC 7540 6.7|https://datatracker.ietf.org/doc/html/rfc7540#section-6.8]
{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)