Reporting issues with virtual threads

[Alan Bateman]

On 21/11/2023 17:34, Philip Boutros wrote:
> Hi
>
> I recently ran into a number of issues with virtual threads as 
> documented in this article.
> https://medium.com/@phil_3582/java-virtual-threads-some-early-gotchas-to-look-out-for-f65df1bad0db?source=friends_link&sk=f1f6ed425c4d17cdc1188f85a0d13d4d 
> <https://medium.com/@phil_3582/java-virtual-threads-some-early-gotchas-to-look-out-for-f65df1bad0db?source=friends_link&sk=f1f6ed425c4d17cdc1188f85a0d13d4d>
> (Friend link, no paywall)
>
> At least two of these issues (HttpClient thread explosion and 
> ReadableByteChannel/HttpResponseInputStream deadlock) 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 https://bugs.openjdk.org/ 
> let alone fix and PR them myself. Some direction would be appreciated.
>

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.

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.

-Alan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20231121/ada67b0f/attachment.htm>