You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by ski n <ra...@gmail.com> on 2026/08/10 10:20:52 UTC
Re: Virtual threads status
Now with the release of 6.3.0 I followed the guide:
https://activemq.apache.org/components/classic/documentation/virtual-threads
I was already on JDK25, updated to 6.3.0 and added
virtualThreadTaskRunner=”true” to activemq.xml. On the broker side I am
good to go.
Some questions:
1. Do they now functionally work non-blocking, similarly to Artemis?
2. I am calling it from Apache Camel as a client, and they have an ActiveMQ
6 component (
https://camel.apache.org/components/next/activemq6-component.html). I
however
use the plain JMS component, so that the client and the broker is always
aligned. Thus, 6.3.0 in this case. Do I need to enable something on the
client side? Or is purely the broker side enough?
3. Small side note, I copied the virtualThreadTaskRunner=”true” property
from the docs, but this wasn't the correct quotes.
Thanks for the great work, virtual threads are a great addition for
ActiveMQ.
Raymond
On Mon, Jul 13, 2026 at 1:33 PM ski n <ra...@gmail.com> wrote:
> OK, that clears it up. Thanks, I'm looking forward to it.
>
> On Fri, Jul 10, 2026 at 8:59 PM Matt Pavlovich <ma...@apache.org>
> wrote:
>
>> Hi Raymond-
>>
>> I completed the Virtual Thread support and committed into the v6.2.0
>> tree. Unfortunately, due to an accidental oversight during the release it
>> was not included. Virtual Thread support is now released as part of a
>> Multi-release jar in the activemq-client, and does not require a separate
>> jar any longer.
>>
>> Since we are following SEMVER more closely with ActiveMQ releases, it
>> will now be officially included in the v6.3.0 release.
>>
>> I’ll update the website with the latest change in how it is released.
>>
>> Thanks,
>> Matt Pavlovich
>>
>> > On Jun 30, 2026, at 11:27 AM, ski n <ra...@gmail.com> wrote:
>> >
>> > Currently the status on the ActiveMQ website states that:
>> >
>> > " ActiveMQ Classic support for Virtual Threads is in Technology Preview
>> > stage. "
>> >
>> >
>> https://activemq.apache.org/components/classic/documentation/virtual-threads
>> >
>> > However the website mentions ActiveMQ 6.1 and JDK21. I am now for
>> example
>> > using ActiveMQ 6.2.7 on JDK25.
>> >
>> > The documentation states that:
>> >
>> > 1. Checkout activemq source code from git
>> > - 2. Build using JDK 21 (Virtual Thread support will be added
>> automatically)
>> > - 3. Replace the lib/activemq-client_version_.jar with the
>> > lib/jdk21/activemq-client-jdk21-_version.jar
>> > -
>> >
>> > 4. Edit conf/activemq.xml
>> >
>> > <broker … virtualThreadTaskRunner=”true” .. >
>> > Does enabling virtual threads still need to build from source? Or can
>> it be
>> > enabled in the regular activemq.xml of a regular build?
>> >
>> > Thanks,
>> >
>> > Raymond
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
>> For additional commands, e-mail: users-help@activemq.apache.org
>> For further information, visit: https://activemq.apache.org/contact
>>
>>
>>
Re: Virtual threads status
Posted by Matt Pavlovich <ma...@apache.org>.
Hi Raymond-
1. Yes, Virtual Threads are fully implemented and the JVM will park threads as it sees fit (mostly for I/O). Keep in mind, I still have it flagged as @Experimental as it is new and we do not have a lot of end-user feedback on various use case scenarios yet. JDK 25 solves the thread-pinning issue, so in general it should “just work”. Probably by 6.4.0 or 6.5.0 the @Experimental will be dropped. So far, I haven’t seen a single hiccup and I’ve been running a ton of heavy topic throughput profiling and testing.
Note that there are several optimizations to boot throughput and further eliminate contention coming in 6.4.0.
2. That’s cool! I was not aware of the updated Camel ActiveMQ 6 component. Client-side virtual threads are not supported yet. I uncovered a client-side hiccup and will be addressing that in 6.4.0 (there is a chance it gets back ported to 6.3.x if its determined to meet ‘bug’ criteria.
3. Please file an issue on https://github.com/apache/activemq-website and I’ll fix it.
Also— For more info, I posted a blog on the v6.3.0 performance boost for topics with Virtual Thread’s and JL’s send topic improvement.
Link:
https://medium.com/javarevisited/how-activemq-v6-3-0-boosts-topic-throughput-up-to-93-6b00006f3b82?sharedUserId=mattrpav
Thanks!
Matt Pavlovich
> On Aug 10, 2026, at 5:20 AM, ski n <ra...@gmail.com> wrote:
>
> Now with the release of 6.3.0 I followed the guide:
>
> https://activemq.apache.org/components/classic/documentation/virtual-threads
>
> I was already on JDK25, updated to 6.3.0 and added
> virtualThreadTaskRunner=”true” to activemq.xml. On the broker side I am
> good to go.
>
> Some questions:
>
> 1. Do they now functionally work non-blocking, similarly to Artemis?
> 2. I am calling it from Apache Camel as a client, and they have an ActiveMQ
> 6 component (
> https://camel.apache.org/components/next/activemq6-component.html). I
> however
> use the plain JMS component, so that the client and the broker is always
> aligned. Thus, 6.3.0 in this case. Do I need to enable something on the
> client side? Or is purely the broker side enough?
> 3. Small side note, I copied the virtualThreadTaskRunner=”true” property
> from the docs, but this wasn't the correct quotes.
>
> Thanks for the great work, virtual threads are a great addition for
> ActiveMQ.
>
> Raymond
>
>
> On Mon, Jul 13, 2026 at 1:33 PM ski n <ra...@gmail.com> wrote:
>
>> OK, that clears it up. Thanks, I'm looking forward to it.
>>
>> On Fri, Jul 10, 2026 at 8:59 PM Matt Pavlovich <ma...@apache.org>
>> wrote:
>>
>>> Hi Raymond-
>>>
>>> I completed the Virtual Thread support and committed into the v6.2.0
>>> tree. Unfortunately, due to an accidental oversight during the release it
>>> was not included. Virtual Thread support is now released as part of a
>>> Multi-release jar in the activemq-client, and does not require a separate
>>> jar any longer.
>>>
>>> Since we are following SEMVER more closely with ActiveMQ releases, it
>>> will now be officially included in the v6.3.0 release.
>>>
>>> I’ll update the website with the latest change in how it is released.
>>>
>>> Thanks,
>>> Matt Pavlovich
>>>
>>>> On Jun 30, 2026, at 11:27 AM, ski n <ra...@gmail.com> wrote:
>>>>
>>>> Currently the status on the ActiveMQ website states that:
>>>>
>>>> " ActiveMQ Classic support for Virtual Threads is in Technology Preview
>>>> stage. "
>>>>
>>>>
>>> https://activemq.apache.org/components/classic/documentation/virtual-threads
>>>>
>>>> However the website mentions ActiveMQ 6.1 and JDK21. I am now for
>>> example
>>>> using ActiveMQ 6.2.7 on JDK25.
>>>>
>>>> The documentation states that:
>>>>
>>>> 1. Checkout activemq source code from git
>>>> - 2. Build using JDK 21 (Virtual Thread support will be added
>>> automatically)
>>>> - 3. Replace the lib/activemq-client_version_.jar with the
>>>> lib/jdk21/activemq-client-jdk21-_version.jar
>>>> -
>>>>
>>>> 4. Edit conf/activemq.xml
>>>>
>>>> <broker … virtualThreadTaskRunner=”true” .. >
>>>> Does enabling virtual threads still need to build from source? Or can
>>> it be
>>>> enabled in the regular activemq.xml of a regular build?
>>>>
>>>> Thanks,
>>>>
>>>> Raymond
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
>>> For additional commands, e-mail: users-help@activemq.apache.org
>>> For further information, visit: https://activemq.apache.org/contact
>>>
>>>
>>>