On Tue, 2 Dec 2025 16:53:23 GMT, Daniel Fuchs <[email protected]> wrote:
> The `jdk.httpclient.quic.maxBidiStreams` is an undocumented system property > only used in tests. This property is only useful to control the default > HTTP/3 test server implementation. It will never be documented or exposed. It > should be clearly labelled as internal. > The HTTP/3 client always provide a value of 0 for the > `initial_max_streams_bidi` transport parameter, so the default value that the > quic stack uses internally to set the parameter if no value is provided is > never used on the client side. > > The `H3StreamLimitReachedTest` can be used to verify the change - it won't > pass if the property is not correctly configured in the test. > > I have also taken this opportunity to add comments to the > `H3StreamLimitReachedTest` and the `StreamLimitTest`, to explain the logic of > each test. > > With this I believe that we can also say that this change will fix > [JDK-8365794](https://bugs.openjdk.org/browse/JDK-8365794). This pull request has now been integrated. Changeset: af8977e4 Author: Daniel Fuchs <[email protected]> URL: https://git.openjdk.org/jdk/commit/af8977e40661db2edec069d524f7c9352c7de850 Stats: 61 lines in 4 files changed: 51 ins; 0 del; 10 mod 8372951: The property jdk.httpclient.quic.maxBidiStreams should be renamed to jdk.internal 8365794: StreamLimitTest vs H3StreamLimitReachedTest: consider renaming or merging Reviewed-by: jpai ------------- PR: https://git.openjdk.org/jdk/pull/28611
