On Mon, 2 Mar 2026 10:51:39 GMT, Daniel Jeliński <[email protected]> wrote:
> Raise the QUIC connection timeout in the H3MultipleConnectionsToSameHost test > above the jtreg timeout. > > The test failed with a QUIC connection timeout, but the reason for the > timeout was not found in the logs. This kind of failure is usually caused by > one of: > - packet loss; when that happens, the congestion controller slows down the > sending rate until the connection times out, > - threading issues like races / deadlocks > - overloaded machine; the threads might not get enough CPU time to respond > before the timeout expires. > > Increasing the QUIC connection timeout should mitigate the packet loss and > CPU issues, and will provide additional information like thread / core dumps > to help with diagnosing threading issues. After apply the proposed patch, test seems more ronustness. The useNioSelector intermittent fails "Connection closed by server peer: INTERNAL_ERROR". Maybe this intermittent was not introdued by the propsoed patch. ------------- PR Review: https://git.openjdk.org/jdk/pull/29993#pullrequestreview-3876396171
