<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>While at it, in your application could you also check what the
server sends for the "max_idle_timeout" QUIC transport parameter
<a class="moz-txt-link-freetext" href="https://www.rfc-editor.org/rfc/rfc9000#section-18.2-4.4.1">https://www.rfc-editor.org/rfc/rfc9000#section-18.2-4.4.1</a>? If
that's not easy to locate, then you could enable (very verbose)
logging of the JDK's HttpClient by setting the
-Djdk.internal.httpclient.debug=true system property and rerunning
the application. It will generate lots of logs, but you could
search for "max_idle_timeout" or even "Received peer Quic
transport params" text in that log.<br>
</p>
<p>-Jaikiran<br>
</p>
<div class="moz-cite-prefix">On 10/11/25 3:29 pm, Jaikiran Pai
wrote:<br>
</div>
<blockquote type="cite" cite="mid:37895ea9-3298-4843-8bf7-04986c0be342@oracle.com">
<p>Hello Josiah,</p>
<p>Nov 08, 2025 11:15:41 AM
jdk.internal.net.http.quic.QuicConnectionImpl pushDatagram<br>
INFO: QUIC: QuicClientConnection(1) OUT: ONERTT(pn:4, size=75,
phase:-1, spin:-1, frames:[StreamFrame(stream=0, offset=0,
length=2, fin=false), StreamFrame(stream=0, offset=2, length=2,
fin=false), StreamFrame(stream=0, offset=4, length=34,
fin=true)])<br>
...<br>
INFO: QUIC: QuicClientConnection(1): APPLICATION no deadline,
task unscheduled<br>
Nov 08, 2025 11:16:11 AM
jdk.internal.net.http.quic.IdleTimeoutManager idleTimedOut<br>
</p>
<p>The long running request, is it generating any response during
those 30 seconds from the server to the client or is it handling
the request on the server side without generating any traffic
during that period. This does look like an issue we need to look
into, so having that detail would help.</p>
<p>-Jaikiran<br>
</p>
<div class="moz-cite-prefix">On 08/11/25 9:53 pm, Josiah Noel
wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAJ_t5UZzWsGUmnt9Q5D1c26HM-8OpCptvt4OS92vw-VisxU9sA@mail.gmail.com">
<div dir="ltr">
<div>Long time no see,</div>
<div><br>
</div>
<div>I was trying a long running request with the new client
and it seems that after 30 seconds it cuts the request,
regardless of whether I specify a longer request timeout. Is
there a different mechanism for configuration?</div>
<div><br>
</div>
<span class="gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Cheers, Josiah.</div>
</div>
<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"persistentProtection":false,"expandedWatermarking":false,"expires":false,"isManaged":false,"sms":false},"attachments":{},"compose-id":"1","compose-window":{"secure":false}}"></div>
</blockquote>
</blockquote>
</body>
</html>