-
Notifications
You must be signed in to change notification settings - Fork 328
Open
Description
When using sttp's HttpClientFs2Backend (which uses JDK's java.net.http.HttpClient) with HTTP/2, high concurrent load causes immediate failures with java.io.IOException: too many concurrent streams instead of queuing requests
JDK HttpClient creates one HTTP/2 connection per host and fails immediately when concurrent requests exceed the server's SETTINGS_MAX_CONCURRENT_STREAMS limit (typically 100). This is a known unresolved JDK bug: https://bugs.openjdk.org/browse/JDK-8225647.
I would expect this setting to work like some backpressure mechanism but not just failing requests(at least not right away and waiting till timeout comes)
Is there any suggestion or workaround for this to be fixed on sttp lvl?
Here is a gist for reproducing the issue
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels