• Home
    • View
    • Login
    This page
    • Normal
    • Export PDF
    • Page Information

    Loading...
  1. Dashboard
  2. Undefined Space
  3. Loom
  4. Getting started

Getting started

  • Created by Alan Bateman, last modified on Apr 21, 2020

Thread API

The following use a static factory method to create a virtual thread, invokes its start method to schedule it, and then invokes the join method to wait for thread to terminate.

    Thread thread = Thread.newThread(Thread.VIRTUAL, () -> System.out.println("hello"));
thread.start();
thread.join();


The Thread.Builder API can also be used to creates virtual thread. The first example creates a virtual thread but does not start it. The second example creates and start the virtual thread.

   Thread thread1 = Thread.builder().virtual().task(() -> System.out.println("hello")).build();
   Thread thread2 = Thread.builder().virtual().task(() -> System.out.println("hi")).start(); 


The Thread.Builder API can also be used to create a ThreadFactory. The ThreadFactory created by the following snippet will create virtual threads named "worker-0", "worker-1", "worker-2", ...

    ThreadFactory factory = Thread.builder().virtual().name("worker", 0).factory();


ExecutorService API

The following creates an ExecutorService that runs each task in its own virtual thread. The example runs two tasks and selects the result of the first task to complete. It uses the try-with-resources construct which blocks in the ExecutorService::close method until all tasks (or virtual threads in this example) have completed.

try (ExecutorService executor = Executors.newUnboundedVirtualThreadExecutor()) {
Callable<String> task1 = () -> "foo";
Callable<String> task2 = () -> "bar";
String result = executor.invokeAny(List.of(task1, task2));
}


Appendix: Differences between regular Threads and virtual Threads

Thread API

  1. VirtualThread always report their priority as NORM_PRIORITY. The priority is not inherited and cannot be changed with the setPriority method.
  2. Virtual threads are daemon threads. Their daemon status cannot be changed with the setDaemon method.
  3. Virtual threads cannot be suspend, resumed or stopped with the Thread suspend, resume and stop APIs.
  4. Virtual threads have no permissions when running with a security manager.
  5. Virtual threads are not active threads in their thread group. The getThreadGroup method returns a ThreadGroup that cannot be destroyed and its enumerate methods do not enumerate the virtual threads in the group.

Networking APIs

If a virtual thread is interrupted when blocked in an I/O operating on a java.net.Socket, ServerSocket or DatagramSocket then it causes IOException to be thrown. 


Overview
Content Tools
ThemeBuilder
  • No labels

Terms of Use
• License: GPLv2
• Privacy • Trademarks • Contact Us

Powered by a free Atlassian Confluence Open Source Project License granted to https://www.atlassian.com/software/views/opensource-community-additional-license-offer. Evaluate Confluence today.

  • Kolekti ThemeBuilder Powered by Atlassian Confluence 8.5.23
  • Kolekti ThemeBuilder printed.by.atlassian.confluence
  • Report a bug
  • Atlassian News
Atlassian
Kolekti ThemeBuilder EngineAtlassian Confluence
{"serverDuration": 166, "requestCorrelationId": "6ff5815a7bbceb71"}