Hi
No plan for virtual threads - this relies on 3rd party libraries and many
other frameworks starting to adopt them as well, which means Java 21 as
minimum base version.
Support for Java 21 is to run on JDK21. JDK17 will be primary supported,
and 21 secondary, that is the plan for this year.
On Fri, Sep 1, 2023 at 9:34 AM ski n <raymondmees...@gmail.com> wrote:
> In integration there is a lot of Async I/O (calling disk, databases, api's
> and other external systems). Though Camel is very fast, it's mostly these
> async I/O calls that take time and eat a lot of platform threads.
>
> For example:
>
> from("direct:start")
> .log("some log") //this takes less than 1 ms
> .setHeader(Exchange.HTTP_URI, constant("http://someapi";)) //this takes
> less than 1 ms
> .to("http://someapi";) //this takes 3 seconds
> .setHeader("Result","Done") //this takes less than 1 ms
> .to("sql://insertindatabase") //this takes less than 1 seconds
> ;
>
> One solution to this is using virtual threads. They are already part of
> Kotlin (coroutines), but now coming to Java as well in Java 21 (release
> 19th September).
>
> In the Camel 4 blog "What's new" it states that:
>
> "We plan to support Java 21 on next LTS released by the end of this year."
>
> Camel next LTS release (4.2) is expected around December.
>
> I was wondering what the plans here are with supporting virtual threads?
> Will they part of 4.2 or planned for later?
>
> Raymond
>
--
Claus Ibsen
-----------------
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
