<div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Thanks Alan</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">I'll follow up with the <span style="font-family:Arial,Helvetica,sans-serif">net-dev on the </span><b><font face="arial, sans-serif">HttpClient </font><span style="font-family:Arial,Helvetica,sans-serif">thread ex</span></b><font face="arial, sans-serif"><b>plosion </b>and </font><b><span style="font-family:Arial,Helvetica,sans-serif">ReadableByteChannel/</span></b><span style="font-family:Arial,Helvetica,sans-serif"><b>HttpResponseInputStream deadlock </b>issues.</span></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><span style="font-family:Arial,Helvetica,sans-serif">On the HTTP/2 issue you reference, it's not at all related to virtual threads (I just happened to find it incidentally) and Google's endpoints do in fact limit the stream count to 100. The problem appears when one wants to go over 100, for a given scheme:host:port there seems to be no way (even using additional HttpClient objects) to establish an additional connection and hence a new 100 streams. Maybe I'll take that one to net-dev too. </span></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div class="gmail_default" style="font-size:small">Thanks</div><div class="gmail_default" style="font-size:small">-P</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 21, 2023 at 1:13 PM Alan Bateman <<a href="mailto:Alan.Bateman@oracle.com">Alan.Bateman@oracle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
On 21/11/2023 17:34, Philip Boutros wrote:<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Hi</div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">I
recently ran into a number of issues with virtual threads as
documented in this article. </div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><a href="https://medium.com/@phil_3582/java-virtual-threads-some-early-gotchas-to-look-out-for-f65df1bad0db?source=friends_link&sk=f1f6ed425c4d17cdc1188f85a0d13d4d" target="_blank">https://medium.com/@phil_3582/java-virtual-threads-some-early-gotchas-to-look-out-for-f65df1bad0db?source=friends_link&sk=f1f6ed425c4d17cdc1188f85a0d13d4d</a><br>
</div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">(Friend
link, no paywall)</div>
<div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br>
</div>
<div class="gmail_default"><font face="arial, sans-serif">At least two of these issues
(HttpClient </font>thread ex<font face="arial, sans-serif">plosion
and </font>ReadableByteChannel/HttpResponseInputStream
deadlock)<span style="font-family:arial,sans-serif"> are in
the Java core libraries but I'm at a loss as to how to
proceed since I don't have Author status to even report them
to <a href="https://bugs.openjdk.org/" target="_blank">https://bugs.openjdk.org/</a>
let alone fix and PR them myself. Some direction would be
appreciated. </span></div>
<br>
</div>
</blockquote>
<br>
Thanks for the link. There are a few things in the article that
don't look right, for example it says that several HttpClient
instances share connections but this isn't so. Another thing is that
the HTTP/2 spec allows a server to impose a limit on the number of
concurrent requests and it looks like this is happening here. I
think it might be useful to start a thread on the OpenJDK net-dev
list with the HTTP related issues as I think it should be possible
to explain most of these.<br>
<br>
On the issues with synchronized and pinning. Yes, this is
problematic right now. There is work in progress to help with this
and we hope to have changes in the loom repo soon for testing.<br>
<br>
-Alan.<br>
</div>
</blockquote></div>