You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/main/asciidoc/virtual-threads.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ For each of them, the object stored in the `ThreadLocal` is created (often large
147
147
This problem leads to high memory usage.
148
148
Unfortunately, it requires sophisticated code changes in the libraries themselves.
149
149
150
-
=== Use @RunVirtualThread with RESTEasy Reactive
150
+
=== Use @RunOnVirtualThread with RESTEasy Reactive
151
151
152
152
This section shows a brief example of using the link:{runonvthread}[@RunOnVirtualThread] annotation.
153
153
It also explains the various development and execution models offered by Quarkus.
@@ -296,7 +296,7 @@ Note that all three models can be used in a single application.
296
296
297
297
== Use virtual thread friendly clients
298
298
299
-
As mentioned in the href:why-not[Why not run everything on virtual threads?] section, the Java ecosystem is not entirely ready for virtual threads.
299
+
As mentioned in the xref:why-not[Why not run everything on virtual threads?] section, the Java ecosystem is not entirely ready for virtual threads.
300
300
So, you need to be careful, especially when using a libraries doing I/O.
301
301
302
302
Fortunately, Quarkus provides a massive ecosystem that is ready to be used in virtual threads.
@@ -375,7 +375,7 @@ mvn package
375
375
376
376
=== Using a local GraalVM installation
377
377
378
-
To compile a Quarkus applications leveraging `@RunOnVirtualThreads` into native executable, you must be sure to use a GraalVM / Mandrel `native-image` supporting virtual threads, so providing at least Java 19+.
378
+
To compile a Quarkus applications leveraging `@RunOnVirtualThread` into native executable, you must be sure to use a GraalVM / Mandrel `native-image` supporting virtual threads, so providing at least Java 19+.
379
379
380
380
Then, until Java 21, you need to add the following property to your `application.properties` file:
381
381
@@ -532,4 +532,4 @@ public class LoomUnitExampleTest {
532
532
533
533
== Additional references
534
534
535
-
- https://dl.acm.org/doi/10.1145/3583678.3596895[Considerations for integrating virtual threads in a Java framework: a Quarkus example in a resource-constrained environment]
535
+
- https://dl.acm.org/doi/10.1145/3583678.3596895[Considerations for integrating virtual threads in a Java framework: a Quarkus example in a resource-constrained environment]
0 commit comments