On Fri, 10 Jan 2025 13:32:39 GMT, Alan Bateman wrote:
> The thread-per-task-executor returned by
> Executors.newVirtualThreadPerTaskExecutor will terminate without waiting for
> threads that are still executing cancelled tasks. This is different to
> ThreadPoolExecutor and ForkJoinPool that wa
On Sat, 11 Jan 2025 07:29:32 GMT, Alan Bateman wrote:
>> test/jdk/java/util/concurrent/ThreadPerTaskExecutor/ThreadPerTaskExecutorTest.java
>> line 306:
>>
>>> 304: stop.await();
>>> 305: return null;
>>> 306: });
>>
>> One (additional?) option would be to obtai
On Fri, 10 Jan 2025 13:32:39 GMT, Alan Bateman wrote:
> The thread-per-task-executor returned by
> Executors.newVirtualThreadPerTaskExecutor will terminate without waiting for
> threads that are still executing cancelled tasks. This is different to
> ThreadPoolExecutor and ForkJoinPool that wa
On Fri, 10 Jan 2025 14:16:44 GMT, Viktor Klang wrote:
>> The thread-per-task-executor returned by
>> Executors.newVirtualThreadPerTaskExecutor will terminate without waiting for
>> threads that are still executing cancelled tasks. This is different to
>> ThreadPoolExecutor and ForkJoinPool tha
The thread-per-task-executor returned by
Executors.newVirtualThreadPerTaskExecutor will terminate without waiting for
threads that are still executing cancelled tasks. This is different to
ThreadPoolExecutor and ForkJoinPool that wait for the threads to finish
executing the cancelled tasks. Not
