Virtual threads in existing FJP logic
ron.pressler at oracle.com
Mon Feb 17 14:33:16 UTC 2020
I’m not sure I understand. You want to use virtual threads as
FJP *workers*? If so, why?
It is never a good idea to pool virtual threads, and FJP is all about
pooling. Of course, you could always set your FJP as the *scheduler*
for your virtual threads.
On 14 February 2020 at 20:26:20, Christian Stein (sormuras at gmail.com(mailto:sormuras at gmail.com)) wrote:
> Hi everybody,
> Marc and I from the JUnit team are exploring ways how to
> integrate virtual threads into the Jupiter test engine. Today
> we're using a FJP to enable parallel test execution.
> Find the implementation here , where at end of the source
> file, you'll see our custom ForkJoinWorkerThreadFactory and
> the custom ForkJoinWorkerThread implementation.
> My idea was to "simply" configure those custom classes to
> create virtual threads. Is this possible? If not, we might
> resort to add a virtual thread based implementation of the
> HierarchicalTestExecutorService interface.
More information about the loom-dev