From d87dcb8312c3c82f9db08e7ff5bca7fc00c4412f Mon Sep 17 00:00:00 2001 From: Clement Escoffier Date: Tue, 10 Oct 2023 07:36:02 +0200 Subject: [PATCH] List specific guides about virtual threads The list was not written yet (there was a TODO). This commit adds the list of dedicated guides about virtual threads. --- docs/src/main/asciidoc/scheduler-reference.adoc | 1 + docs/src/main/asciidoc/virtual-threads.adoc | 7 ++++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/scheduler-reference.adoc b/docs/src/main/asciidoc/scheduler-reference.adoc index f32e6f534d0e0..daa83f030cb74 100644 --- a/docs/src/main/asciidoc/scheduler-reference.adoc +++ b/docs/src/main/asciidoc/scheduler-reference.adoc @@ -417,6 +417,7 @@ If the xref:smallrye-metrics.adoc[SmallRye Metrics extension] is present, then a If `quarkus.scheduler.tracing.enabled` is set to `true` and the xref:opentelemetry.adoc[OpenTelemetry extension] is present then the `@io.opentelemetry.instrumentation.annotations.WithSpan` annotation is added automatically to every `@Scheduled` method. As a result, each execution of this method has a new `io.opentelemetry.api.trace.Span` associated. +[[virtual_threads]] == Run @Scheduled methods on virtual threads Methods annotated with `@Scheduled` can also be annotated with `@RunOnVirtualThread`. diff --git a/docs/src/main/asciidoc/virtual-threads.adoc b/docs/src/main/asciidoc/virtual-threads.adoc index 95223c68b3f49..113a26c92e05e 100644 --- a/docs/src/main/asciidoc/virtual-threads.adoc +++ b/docs/src/main/asciidoc/virtual-threads.adoc @@ -80,7 +80,12 @@ It will either reduce the chance for the other virtual thread to run or will sta In Quarkus, the support of virtual thread is implemented using the link:{runonvthread}[@RunOnVirtualThread] annotation. This section briefly overviews the rationale and how to use it. -There are dedicated guides for extensions supporting that annotation, such as // TODO. +There are dedicated guides for extensions supporting that annotation, such as: + +- xref:./resteasy-reactive-virtual-threads.adoc[Virtual threads in REST applications] +- xref:./messaging-virtual-threads.adoc[Virtual threads in reactive messaging applications] +- xref:./grpc-virtual-threads.adoc[Virtual threads in gRPC services] +- xref:./scheduler-reference.adoc#virtual_threads[Execute periodic tasks on virtual threads] [[why-not]] === Why not run everything on virtual threads?