formula: (connectionCount
– keepAliveCount)
is still considered a reliable way to determine the number of virtual threads
that are created or active at any point in time when using
useVirtualThreads="true".
I would appreciate any insights or clarifications on this.
Thanks,
Rose Mary
whether the following executor and connector setup in Tomcat 10.1.36 is
correct?
className="org.apache.catalina.core.StandardVirtualThreadExecutor"/>
That should work. Although I do wonder on why you have configured an
executor here. There isn't really any point with vir
Hi Mark,
I hope this message finds you well.
I just wanted to send a quick reminder regarding the email I sent on 3rd
April,2025 about Monitoring Virtual Threads via JMX / MBeans in Tomcat . If you
haven’t had the chance to review it yet, I would greatly appreciate your
thoughts or any updates
#workerThreadName. Please
see the screenshot :
* [cid:image001.png@01DBA4BE.812049C0]
I would greatly appreciate your insight into this matter, especially if the
configuration provided requires any adjustments or if there are specific
conditions I need to be aware of for the virtual threads to function as
fic
aspects to investigate further. Any guidance on what to focus on next would be
greatly appreciated.
Additionally, could you suggest if there is any MBean attribute that can help
identify whether the threads being used are virtual threads or platform threads?
For Tomcat requests, the curr
e, and the connectionCount remains at 1.
I’d appreciate any additional guidance on where I should focus next, or if
there are other specific aspects I should investigate further.
Also, any suggestions on an MBean attribute to differentiate between virtual
threads and platform threads would be real
nally, could you suggest if there is any MBean attribute that can help
identify whether the threads being used are virtual threads or platform threads?
Thank you for your continued support.
Best Regards,
Rose Mary
From: Mark Thomas
Date: Thursday, 27 March 2025 at 9:25 PM
To: users@tomcat.apach
created a sample Spring Boot application that continuously creates
virtual threads in a loop.
If the application is creating the threads then this won't work. The
(connectionCount - keepAliveCount) approach only works for virtual
threads created by Tomcat for processing requests.
I
continuously creates
virtual threads in a loop.
* The application was deployed in the TOMCAT_LOCATION/webapps directory and
started on localhost.
In Apache Tomcat 10.1.36, we added the following configuration to the
server.xml file to enable virtual threads:
Its observed in the logs that
continuously creates
virtual threads in a loop.
* The application was deployed in the TOMCAT_LOCATION/webapps directory and
started on localhost.
In Apache Tomcat 10.1.36, we added the following configuration to the
server.xml file to enable virtual threads:
Its observed in the logs that
alternate ways with which we can monitor this from tomcat side.?
(connectionCount - keepAliveCount) should be a reasonable estimate of
the virtual threads currently being used.
If the requests are synchronous (and there is little point using virtual
threads with async requests) then the creation
Clarification:
We have configured Tomcat 10.1.33 with,
While this works, the existing ThreadPool MBeans show currentThreadsBusy=-1 and
maxThreads=200 (incorrect in case of virtual threads). Is this expected
behavior?
JVM vs. Tomcat Metrics:
We observe that the JVM’s java.lang.management.ThreadMXBean
Clarification:
We have configured Tomcat 10.1.33 with,
While this works, the existing ThreadPool MBeans show currentThreadsBusy=-1 and
maxThreads=200 (incorrect in case of virtual threads). Is this expected
behavior?
JVM vs. Tomcat Metrics:
We observe that the JVM’s java.lang.management.ThreadMXBean
All,
On 1/21/25 7:12 AM, Mark Thomas wrote:
On 21/01/2025 11:17, joan.balagu...@ventusproxy.com wrote:
Hi,
Virtual threads only shine on I/O bound tasks, in terms of throughput
(not latency). They were created for that, don't expect any
improvement on CPU bound tasks.
+1.
If I h
On 21/01/2025 11:17, joan.balagu...@ventusproxy.com wrote:
Hi,
Virtual threads only shine on I/O bound tasks, in terms of throughput (not
latency). They were created for that, don't expect any improvement on CPU bound
tasks.
+1.
If I had to guess, I'd guess something to do with c
Hi,
Virtual threads only shine on I/O bound tasks, in terms of throughput (not
latency). They were created for that, don't expect any improvement on CPU bound
tasks.
Regards,
Joan.
-Original Message-
From: Owner
Sent: Tuesday, January 21, 2025 11:32 AM
To: Tomcat Users
5 at 16:40, Owner wrote:
>
> > Hey Tomcat,
> >
> > Andy here. I'm not sure if this is the place to ask this question, but I
> > wanted to check regarding performances of virtual threads vs using a
> > conventional worker thread pool.
> >
> > I se
your image was dropped :((
please use some image image service and provide the URL here :))
On Tue, 21 Jan 2025 at 16:40, Owner wrote:
> Hey Tomcat,
>
> Andy here. I'm not sure if this is the place to ask this question, but I
> wanted to check regarding performances of virtual
Hey Tomcat,
Andy here. I'm not sure if this is the place to ask this question, but I
wanted to check regarding performances of virtual threads vs using a
conventional worker thread pool.
I set up an endpoint with a CPU task of calculating factorials like the
below:
@GetMapping(&quo
On 07/09/2023 15:41, Christopher Schultz wrote:
On 9/6/23 16:29, Mark Thomas wrote:
There isn't
much point using an executor with virtual threads.
Okay then perche
https://tomcat.apache.org/tomcat-11.0-doc/config/executor.html#Virtual_Thread_Implementation ?
That is the int
quot;virtual" anywhere on that page.
It is a Connector attribute, not an Executor attribute. There isn't much
point using an executor with virtual threads.
Okay then perche
https://tomcat.apache.org/tomcat-11.0-doc/config/executor.html#V
It is a Connector attribute, not an Executor attribute. There isn't much
point using an executor with virtual threads.
For those of you that are finding this topic interesting, I'll have a
talk on this at the ASF conference, Community Over Code in Halifax.
https://communityovercode.
Mark,
On 9/6/23 03:29, Mark Thomas wrote:
On 05/09/2023 22:02, Christopher Schultz wrote:
Mark,
On 9/5/23 15:55, Mark Thomas wrote:
On 05/09/2023 20:38, Christopher Schultz wrote:
All,
I have some questions about Virtual Threads and their use within
Tomcat. Note that only Tomcat 11
On 05/09/2023 22:02, Christopher Schultz wrote:
Mark,
On 9/5/23 15:55, Mark Thomas wrote:
On 05/09/2023 20:38, Christopher Schultz wrote:
All,
I have some questions about Virtual Threads and their use within
Tomcat. Note that only Tomcat 11 currently has support for Virtual
Threads when
Mark,
On 9/5/23 15:55, Mark Thomas wrote:
On 05/09/2023 20:38, Christopher Schultz wrote:
All,
I have some questions about Virtual Threads and their use within
Tomcat. Note that only Tomcat 11 currently has support for Virtual
Threads when running on a version 19 or later JVM.
Not quite
On 05/09/2023 20:38, Christopher Schultz wrote:
All,
I have some questions about Virtual Threads and their use within Tomcat.
Note that only Tomcat 11 currently has support for Virtual Threads when
running on a version 19 or later JVM.
Not quite. All current versions support virtual threads
All,
I have some questions about Virtual Threads and their use within Tomcat.
Note that only Tomcat 11 currently has support for Virtual Threads when
running on a version 19 or later JVM.
My (admittedly limited) understanding is that the use of Virtual
Threads, specifically within Tomcat
st release to test.
Regards.
El jue, 6 jul 2023 a las 15:13, Mark Thomas ()
escribió:
6 Jul 2023 20:09:01 Daniel Andres Pelaez Lopez :
I am aware Tomcat community did a great effort to move Tomat to
Virtual Threads friendly, but I am not sure why HTTP2 was not part of
that effort?
The plan
;
> >>> Regards.
> >>>
> >>>
> >>> El jue, 6 jul 2023 a las 15:13, Mark Thomas ()
> >>> escribió:
> >>>>
> >>>>
> >>>> 6 Jul 2023 20:09:01 Daniel Andres Pelaez Lopez :
> >>>>
> >
es Pelaez Lopez wrote:
Mark,
Thanks for letting me know. I will wait for the August release to test.
Regards.
El jue, 6 jul 2023 a las 15:13, Mark Thomas ()
escribió:
6 Jul 2023 20:09:01 Daniel Andres Pelaez Lopez :
I am aware Tomcat community did a great effort to move Tomat to
Virtual T
id a great effort to move Tomat to
Virtual Threads friendly, but I am not sure why HTTP2 was not part of
that effort?
The plan was always to see where the bottlenecks were as folks start to
experiment with Loom support and fix issues as they arose. It helps
focus
effort on where it is really need
release to test.
Regards.
El jue, 6 jul 2023 a las 15:13, Mark Thomas () escribió:
6 Jul 2023 20:09:01 Daniel Andres Pelaez Lopez :
I am aware Tomcat community did a great effort to move Tomat to
Virtual Threads friendly, but I am not sure why HTTP2 was not part of
that effort?
The plan was
Mark,
Thanks for letting me know. I will wait for the August release to test.
Regards.
El jue, 6 jul 2023 a las 15:13, Mark Thomas () escribió:
>
>
> 6 Jul 2023 20:09:01 Daniel Andres Pelaez Lopez :
>
> > I am aware Tomcat community did a great effort to move Tomat to
&
6 Jul 2023 20:09:01 Daniel Andres Pelaez Lopez :
I am aware Tomcat community did a great effort to move Tomat to
Virtual Threads friendly, but I am not sure why HTTP2 was not part of
that effort?
The plan was always to see where the bottlenecks were as folks start to
experiment with Loom
Hi community,
I am working on a Spring Boot + Tomcat embedded application using
Virtual Threads (https://openjdk.org/jeps/425), and everything looks
great until we activate HTTP2. We started to see the following logs:
Thread[#72,ForkJoinPool-1-worker-9,5,CarrierThreads
35 matches
Mail list logo
