Virtual threads in existing FJP logic
sormuras at gmail.com
Sat Feb 15 21:18:58 UTC 2020
the issue I see is that the ForkJoinWorkerThreadFactory declares
a method newThread with ForkJoinWorkerThread as the return type.
That ForkJoinWorkerThread already extends java.lang.Thread, see
 for details. The API of ForkJoinWorkerThread doesn't allow
setting a virtual flag nor does the Thread.Builder help in this regard.
On Sat, Feb 15, 2020 at 10:57 AM Nawazish Khan <md.nawazish.khan at gmail.com>
> Hi Christian,
> I believe it should be possible and doable. The Worker Thread Facrory,
> while creating Threads, should simply create Virtual Threads instead of
> On Sat, Feb 15, 2020 at 1:56 AM Christian Stein <sormuras at gmail.com>
>> 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