RFR: 8350279: HttpClient: Add a new HttpResponse method to identify connections [v12]

Volkan Yazici vyazici at openjdk.org
Tue Apr 15 09:28:05 UTC 2025


On Tue, 15 Apr 2025 07:31:32 GMT, Volkan Yazici <vyazici at openjdk.org> wrote:

>> If no executor is provided the HTTP/2 server will create its own. The HTTP/1.1 server however will run the exchange in the dispacher thread - so you need to at least provide an executor for the HTTP/1.1 server if you don't want to wedge when making parallel requests. But not the common FJP ;-)
>
> In a0859c7c68614e8c3f531b1d4d9357f3f48cf5ab,
> 
> - Used a dedicated executor (!= FJP) only for HTTP/1.1 servers (also documented the rationale in the sources)
> - Added `SystemDiagnosticsCollector` to aid with troubleshooting
> 
> Verified that test passes on Windows, Linux, and macOS hosts with 30 repetitions.

After consulting @jaikiran, removed `SystemDiagnosticsCollector` in ad73d38cd0382308224f721722367fd289fdc9d5. I will separately explore the possibilities of adding a similar troubleshooting tool in a more generic fashion.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/24154#discussion_r2044086645


More information about the net-dev mailing list