JVM crash using virtual threads with Camel http client

[Jonathan Henson]

Hi,

This relates to a Windows build of JDK 17:

Java VM: OpenJDK 64-Bit Server VM (17-loom+7-342, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)

I've been attempting to benchmark the performance of simple http interactions with Camel using virtual threads.  On the server side of things, I haven't seen any problems using the Jetty component configured to use a ThreadPool that creates an executor using:

Executors.newThreadExecutor(Thread.ofVirtual().factory())

On the client side, using an executor created as above leads to the process locking up after a few thousand requests.  In one instance, the JVM crashed:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc67d16cf0, pid=83320, tid=33044
#
# JRE version: OpenJDK Runtime Environment (17.0+7) (build 17-loom+7-342)
# Java VM: OpenJDK 64-Bit Server VM (17-loom+7-342, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# [thread 170664 also had an error]
[thread 119408 also had an error]
V  [jvm.dll+0x646cf0]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# E:\loom\eclipse\camel-loom\hs_err_pid83320.log
[thread 33388 also had an error]
[thread 182020 also had an error]
#
# If you would like to submit a bug report, please visit:
#   https://bugreport.java.com/bugreport/crash.jsp
#

I've attached the project that I've been using, and this includes the hs_err_pid83320.log mentioned above.

Regards,
Jon


::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________