-
Enhancement
-
Resolution: Fixed
-
P4
-
24
-
b21
The java.net.http.HttpClient tests use two HTTP server implementations:
1. HTTP/1.1 server implementation provide by the jdk.httpserver module
2. HTTP/2 test server implementation (i.e., `jdk.httpclient.test.lib.http2.Http2TestServer`) used _only_ for HTTP/2 tests
The HTTP/1.1 server is not multi-threaded by default – except the main dispatcher thread. But it accepts an executor that could be configured to create thread that include a server name.
The HTTP/2 server is created with a _name_, is multi-threaded, yet names of its threads don't include a reference to the server name. This story aims to improve the diagnostics by including the server name in the HTTP/2 server thread names.
Note that porting this to the `http3` branch will need adaptation in `jdk.httpclient.test.lib.quic.QuicServer`.
1. HTTP/1.1 server implementation provide by the jdk.httpserver module
2. HTTP/2 test server implementation (i.e., `jdk.httpclient.test.lib.http2.Http2TestServer`) used _only_ for HTTP/2 tests
The HTTP/1.1 server is not multi-threaded by default – except the main dispatcher thread. But it accepts an executor that could be configured to create thread that include a server name.
The HTTP/2 server is created with a _name_, is multi-threaded, yet names of its threads don't include a reference to the server name. This story aims to improve the diagnostics by including the server name in the HTTP/2 server thread names.
Note that porting this to the `http3` branch will need adaptation in `jdk.httpclient.test.lib.quic.QuicServer`.
- links to
-
Commit(master) openjdk/jdk/7d9a4383
-
Review(master) openjdk/jdk/24822