Re: Monitoring Virtual Threads via JMX / MBeans in Tomcat

On Thu, Jun 26, 2025 at 6:23 AM Rose Mary P T wrote: > > Dear Rémy Maucherat, > > > > Thank you for your comments. I have another question: can we configure both > virtual threads and platform threads in the same Apache Tomcat server.xml > file? Specifically, is i

RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat

Dear Rémy Maucherat, Thank you for your comments. I have another question: can we configure both virtual threads and platform threads in the same Apache Tomcat server.xml file? Specifically, is it possible to set up one connector to support an application using virtual threads, and another

Re: Monitoring Virtual Threads via JMX / MBeans in Tomcat

the connectioncount. But > the KeepAliveCount was always showing as zero. Given this behavior, I’m > curious to know whether the formula: (connectionCount – keepAliveCount) > > Can we consider using ProtocolHandler.connectionCount to fetch the virtual > threads created instead.

RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat

curious to know whether the formula: (connectionCount – keepAliveCount) Can we consider using ProtocolHandler.connectionCount to fetch the virtual threads created instead. Please let me know if you need any further information from my side. Looking forward to your response Regards, Rose Mary

RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat

2025 at 7:08 PM To: Tomcat Users List , ma...@apache.org Subject: [EXTERNAL] RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat Dear Tomcat Users/Mark, I was finally able to retrieve the thread name from the workerThreadName attribute in RequestProcessor.tomcatExecutor for a request. In order

RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

Re: Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat

#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

Re: Monitoring Virtual Threads via JMX / MBeans in Tomcat

On 28/03/2025 09:08, Rose Mary P T wrote: Hi Mark, Thank you for the confirmation. As per your suggestion, I have modified the deployed application so that it no longer spawns any threads but instead executes a few calls. Please clarify what you mean by "executes a few calls". Ad

RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

RE: Monitoring Virtual Threads via JMX / MBeans in Tomcat

Hi Mark, Thank you for the confirmation. As per your suggestion, I have modified the deployed application so that it no longer spawns any threads but instead executes a few calls. Additionally, I kept the previous executor and connection configurations for Tomcat. However, I still do not see

Re: Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

Re: Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

Re: Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

Re: Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

Monitoring Virtual Threads via JMX / MBeans in Tomcat

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

Re: Tomcat Virtual Threads Performance

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

Re: Tomcat Virtual Threads Performance

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

RE: Tomcat Virtual Threads Performance

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

Re: Tomcat Virtual Threads Performance

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

Re: Tomcat Virtual Threads Performance

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

Tomcat Virtual Threads Performance

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

Re: [10.1.4] NIO threads seem to hang inexplicably

Mark and Martynas, On 12/11/24 3:20 AM, Mark Thomas wrote: On 10/12/2024 20:22, Martynas Jusevičius wrote: Hi, I recently noticed some weird "gaps" in the logs of my JAX-RS application running on Jersey running on Tomcat (running on Docker): 15:25:06,912 [http-nio-7070-exec-9] DEBUG Applic

Re: [10.1.4] NIO threads seem to hang inexplicably

On 10/12/2024 20:22, Martynas Jusevičius wrote: Hi, I recently noticed some weird "gaps" in the logs of my JAX-RS application running on Jersey running on Tomcat (running on Docker): 15:25:06,912 [http-nio-7070-exec-9] DEBUG ApplicationFilter:135 - Request URI ha

[10.1.4] NIO threads seem to hang inexplicably

Hi, I recently noticed some weird "gaps" in the logs of my JAX-RS application running on Jersey running on Tomcat (running on Docker): 15:25:06,912 [http-nio-7070-exec-9] DEBUG ApplicationFilter:135 - Request URI has not matched any lapp:Dataset 15:25:15,759 [http-nio

RE: Tomcat 10.1.30 and Many Timed Waiting threads

: Christopher Schultz Sent: Monday, September 30, 2024 5:39 PM To: users@tomcat.apache.org Subject: Re: Tomcat 10.1.30 and Many Timed Waiting threads [You don't often get email from ch...@christopherschultz.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] CA

Re: Tomcat 10.1.30 and Many Timed Waiting threads

John, On 9/30/24 13:34, John Williams wrote: No - I cannot see any other thread stuck on DB/external resources. The application functions as expected, just that I see these threads increasing over time. The problem was 1st noticed in Tomcat 10.1.26/OpenJRE 17.0.5 and I've tried movi

RE: Tomcat 10.1.30 and Many Timed Waiting threads

Hi Chuck, No - I cannot see any other thread stuck on DB/external resources. The application functions as expected, just that I see these threads increasing over time. The problem was 1st noticed in Tomcat 10.1.26/OpenJRE 17.0.5 and I've tried moving to Tomcat 10.1.30/OpenJRE 17.0.12 wi

Re: Tomcat 10.1.30 and Many Timed Waiting threads

> On Sep 30, 2024, at 12:15, John Williams > wrote: > > I had an executor defined before and it had the exact same behavior/problem. > Moved to the below model for the connector only after that. The OP didn’t mention the real problem in his original message; it only showed up as almost an

RE: Tomcat 10.1.30 and Many Timed Waiting threads

: Re: Tomcat 10.1.30 and Many Timed Waiting threads [You don't often get email from ch...@christopherschultz.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] CAUTION: This email originated from outside of the organization. Do not click links or open attach

Re: Tomcat 10.1.30 and Many Timed Waiting threads

John, On 9/30/24 10:53, John Williams wrote: Sorry - didn't realize that images would be stripped off. The number of TIMED_WAITING threads starts at 150 or so and every hour increases by 10. Below is an example of where the threads are stuck (by looking at the JVM stack): https-jsse

RE: Tomcat 10.1.30 and Many Timed Waiting threads

Chris, Sorry - didn't realize that images would be stripped off. The number of TIMED_WAITING threads starts at 150 or so and every hour increases by 10. Below is an example of where the threads are stuck (by looking at the JVM stack): https-jsse-nio2-443-exec-90 TIMED_WAITI

Re: Tomcat 10.1.30 and Many Timed Waiting threads

John, On 9/30/24 10:30, John Williams wrote: The issue is that the number of threads in the TIMED_WAIT state keeps increasing over time. Starts at 150 and keeps growing by 10 every hour. Once it reaches close to the maxThreads setting we see connection drops. This application was working

RE: Tomcat 10.1.30 and Many Timed Waiting threads

Chris, Thanks for your response. The issue is that the number of threads in the TIMED_WAIT state keeps increasing over time. Starts at 150 and keeps growing by 10 every hour. Once it reaches close to the maxThreads setting we see connection drops. This application was working fine with

Re: Tomcat 10.1.30 and Many Timed Waiting threads

John, On 9/28/24 05:38, John Williams wrote: Hi Everyone, I am running Apache Tomcat 10.1.30 for a web application and notice ~950 timed_waiting threads. The stack trace for these threads is below: java.base@17.0.12/jdk.internal.misc.Unsafe.park(Native<mailto:java.base@17.0

Tomcat 10.1.30 and Many Timed Waiting threads

Hi Everyone, I am running Apache Tomcat 10.1.30 for a web application and notice ~950 timed_waiting threads. The stack trace for these threads is below: java.base@17.0.12/jdk.internal.misc.Unsafe.park(Native<mailto:java.base@17.0.12/jdk.internal.misc.Unsafe.park(Native> Method); jav

RE: When does Tomcat add and remove threads?

Yes the standard JDK ThreadPoolExecutor behavior is bad. Here is a good thread describing how to fix ThreadPoolExecutor to behave how it should be. https://stackoverflow.com/questions/19528304/how-to-get-the-threadpoolexecutor-to-increase-threads-to-max-before-queueing Obviously Tomcat had to

Re: When does Tomcat add and remove threads?

On Tue, Mar 12, 2024 at 5:55 PM wrote: > > All, > > > > -Original Message- > > From: Christopher Schultz > > Sent: Tuesday, March 12, 2024 8:31 AM > > To: users@tomcat.apache.org > > Subject: Re: When does Tomcat add and remove threads? > &g

RE: When does Tomcat add and remove threads?

All, > -Original Message- > From: Christopher Schultz > Sent: Tuesday, March 12, 2024 8:31 AM > To: users@tomcat.apache.org > Subject: Re: When does Tomcat add and remove threads? > > John, > > On 3/11/24 18:14, john.e.gr...@wellsfargo.com.INVALID wrote: &g

Re: When does Tomcat add and remove threads?

John, On 3/11/24 18:14, john.e.gr...@wellsfargo.com.INVALID wrote: From: Christopher Schultz Sent: Monday, March 11, 2024 5:09 PM > On 3/11/24 17:47, john.e.gr...@wellsfargo.com.INVALID wrote: I am using Tomcat 9.x. When does Tomcat add and remove threads from its internal thread p

Re: When does Tomcat add and remove threads?

Chris, From: Christopher Schultz Sent: Monday, March 11, 2024 5:09 PM To: users@tomcat.apache.org Subject: Re: When does Tomcat add and remove threads? John, On 3/11/24 17:47, john.e.gr...@wellsfargo.com.INVALID wrote: > I am using Tomcat 9.x. > >

Re: When does Tomcat add and remove threads?

John, On 3/11/24 17:47, john.e.gr...@wellsfargo.com.INVALID wrote: I am using Tomcat 9.x. When does Tomcat add and remove threads from its internal thread pool? I'm talking about the threads with names like http-nio-8080-exec-1. It appears the thread pool is Tomcat's own ThreadPo

When does Tomcat add and remove threads?

I am using Tomcat 9.x. When does Tomcat add and remove threads from its internal thread pool? I'm talking about the threads with names like http-nio-8080-exec-1. It appears the thread pool is Tomcat's own ThreadPoolExecutor but I don't see the exact behavior documented. I&

Re: Virtual Threads

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

Re: Virtual Threads

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

Re: Virtual Threads

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.

Re: Virtual Threads

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

Re: Virtual Threads

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

Re: Virtual Threads

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

Re: Virtual Threads

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

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

Re: Pinned threads for HTTP2 using Virtual Threads on Tomcat 10.1.7

mas wrote: Daniel, How did you trigger the pinning? I'm running some basic tests with -Djdk.tracePinnedThreads=short and I'm not seeing any pinned threads reported. Mark On 07/07/2023 13:45, Daniel Andres Pelaez Lopez wrote: Mark, Thanks for letting me know. I will wait for the Augu

Re: Pinned threads for HTTP2 using Virtual Threads on Tomcat 10.1.7

> > Mark > > > > > > On 25/07/2023 10:19, Mark Thomas wrote: > >> Daniel, > >> > >> How did you trigger the pinning? I'm running some basic tests with > >> -Djdk.tracePinnedThreads=short and I'm not seeing any pinned threads >

Re: Pinned threads for HTTP2 using Virtual Threads on Tomcat 10.1.7

I hit send I managed to trigger the issue. Mark On 25/07/2023 10:19, Mark Thomas wrote: Daniel, How did you trigger the pinning? I'm running some basic tests with -Djdk.tracePinnedThreads=short and I'm not seeing any pinned threads reported. Mark On 07/07/2023 13:45, Daniel Andr

Re: Pinned threads for HTTP2 using Virtual Threads on Tomcat 10.1.7

Never mind. Pretty much as soon as I hit send I managed to trigger the issue. Mark On 25/07/2023 10:19, Mark Thomas wrote: Daniel, How did you trigger the pinning? I'm running some basic tests with -Djdk.tracePinnedThreads=short and I'm not seeing any pinned threads reported.

Re: Pinned threads for HTTP2 using Virtual Threads on Tomcat 10.1.7

Daniel, How did you trigger the pinning? I'm running some basic tests with -Djdk.tracePinnedThreads=short and I'm not seeing any pinned threads reported. Mark On 07/07/2023 13:45, Daniel Andres Pelaez Lopez wrote: Mark, Thanks for letting me know. I will wait for the August

Re: Pinned threads for HTTP2 using Virtual Threads on Tomcat 10.1.7

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 &

Re: Pinned threads for HTTP2 using Virtual Threads on Tomcat 10.1.7

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

Pinned threads for HTTP2 using Virtual Threads on Tomcat 10.1.7

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

Re: tomcats starting with 200 threads

: On Mon, Sep 19, 2022 at 7:45 PM Christopher Schultz < ch...@christopherschultz.net> wrote: Jon, On 9/19/22 10:46, Jonathan Yom-Tov wrote: Sometimes one of our production Tomcats will start with the maximum (200) number of threads

Re: tomcats starting with 200 threads

onathan Yom-Tov wrote: > > Sometimes one of our production Tomcats will start with the maximum (200) > > number of threads in the https pool. That is, it doesn't start with some > > minimum and works its way up to the maximum, it immediately starts with > the > > maxi

Re: tomcats starting with 200 threads

Jon, On 9/19/22 10:46, Jonathan Yom-Tov wrote: Sometimes one of our production Tomcats will start with the maximum (200) number of threads in the https pool. That is, it doesn't start with some minimum and works its way up to the maximum, it immediately starts with the maximum. There

Re: tomcats starting with 200 threads

If the machine / VM / container you are running Tomcat on can't handle 200 threads you should be using a smaller value for maxThreads. Mark On 19/09/2022 15:46, Jonathan Yom-Tov wrote: hi, Sometimes one of our production Tomcats will start with the maximum (200) number of threads i

tomcats starting with 200 threads

hi, Sometimes one of our production Tomcats will start with the maximum (200) number of threads in the https pool. That is, it doesn't start with some minimum and works its way up to the maximum, it immediately starts with the maximum. There's no reason for it since most of the threads

Re: [OT] Running out of httpd worker threads (was: WELCOME to users@tomcat.apache.org)

Sahil, On 5/11/22 13:56, Verma, Sahil wrote: In our production environment, ApacheTomcat services went down. We have checked the logs and found below error - [Thu May 05 10:34:51.441668 2022] [mpm_event:error] [pid 27440:tid 140464737793792] AH00484: server reached MaxRequestWorkers setting, co

RE: clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

Thomas > Sent: Monday, August 23, 2021 3:06 AM > To: users@tomcat.apache.org > Subject: Re: clearReferencesThreads issues warning about 2 threads, > spawned by JDK in printing components > > On 23/08/2021 08:10, Thomas Hoffmann (Speed4Trade GmbH) wrote: > > > > >

Re: clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

Mark, On 8/23/21 04:05, Mark Thomas wrote: On 23/08/2021 08:10, Thomas Hoffmann (Speed4Trade GmbH) wrote: Is there anything, the application can prevent this? Yes. Call Thread.setContextClassLoader(ClassLoader) before calling the code that creates those threads, passing the common class

AW: clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

> Is there anything, the application can prevent this? Yes. Call Thread.setContextClassLoader(ClassLoader) before calling the code that creates those threads, passing the common class loader. Afterwards, reset the TCCL back to the web application class loader. > Should Tomcat maybe sk

Re: clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

On 23/08/2021 08:10, Thomas Hoffmann (Speed4Trade GmbH) wrote: Is there anything, the application can prevent this? Yes. Call Thread.setContextClassLoader(ClassLoader) before calling the code that creates those threads, passing the common class loader. Afterwards, reset the TCCL back to

clearReferencesThreads issues warning about 2 threads, spawned by JDK in printing components

, patts); This triggers the JDK to spawn two threads, which can be seen in the OpenJDK-Sources: https://github.com/AdoptOpenJDK/openjdk-jdk11/blob/master/src/java.desktop/windows/classes/sun/print/PrintServiceLookupProvider.java (see around line no 134 ff) --> Thread thr = new Thread(null,

Re: No Logger information when maximum threads reached. Tomcat 8

hes maximum thread limit. Our application is deployed in > tomcat. Maximum thread limit of tomcat is 200,  so If 200 threads are > reached, does tomcat provide any logger information? > >   > > We tried making multiple rest calls and reducing max threads to 2-3. We > fa

No Logger information when maximum threads reached. Tomcat 8

Hi, We have a usecase where we want that our application should indicate when it reaches maximum thread limit. Our application is deployed in tomcat. Maximum thread limit of tomcat is 200, so If 200 threads are reached, does tomcat provide any logger information? We tried making multiple

Re: Enable Logging to Print Max Threads

Screenshots don't make it to this list. You gotta use text to communicate. If it's not important to know the exact moment you hit your high-water mark, you could poll Tomcat via JMX to find out what the current max-threads is and the current active-threads. If you have active-threa

Enable Logging to Print Max Threads

Hi, We are using Tomcat Version : 8.5.53. OS Name:Linux OS Version: 3.10.0-1127.18.2.el7.x86_64 We have a requirement where we wanted a logger to get printed in Catalina.out when Tomcat reaches it's max thread limit. We reduced values of properties : minSpareThreads, maxThreads and

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 David, On 8/27/20 18:14, David wrote: >> I used the http to 8080 in order to read the Tomcat webmanager >> stats. I originally had issues with the JVM being too small, >> running out of memory, CPU spiking, threads maxing out, a

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

>> On 8/27/20 10:48, David wrote: > >>>>>>> In the last two weeks I've had two occurrences where a > >>>>>>> single CentOS 7 production server hosting a public > >>>>>>> webpage has become unresponsive. The first time, a

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

7, 2020 at 12:35 PM Christopher Schultz >>>> wrote: >>>>> >>>> David, >>>> >>>> On 8/27/20 10:48, David wrote: >>>>>>> In the last two weeks I've had two occurrences where a >>>>>>> single CentOS

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

>> > > David, > > > > On 8/27/20 10:48, David wrote: > >>>> In the last two weeks I've had two occurrences where a > >>>> single CentOS 7 production server hosting a public webpage > >>>> has become unresponsive. The first ti

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

single >>> CentOS 7 production server hosting a public webpage has become >>> unresponsive. The first time, all 300 available >>> "https-jsse-nio-8443" threads were consumed, with the max age >>> being around 45minutes, and all in a "S" status.

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

>>>> single CentOS 7 production server hosting a public webpage >>>> has become unresponsive. The first time, all 300 available >>>> "https-jsse-nio-8443" threads were consumed, with the max age >>>> being around 45minutes, and all in a

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

ll 300 available > > "https-jsse-nio-8443" threads were consumed, with the max age being > > around 45minutes, and all in a "S" status. This time all 300 were > > consumed in "S" status with the oldest being around ~16minutes. A > > restart of To

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

On 27/08/2020 18:57, David wrote: > On Thu, Aug 27, 2020 at 12:35 PM Christopher Schultz > wrote: >>>> Is there a graceful way to script the termination of threads in >>>> case Tomcat isn't able to for whatever reason? > > Not really. What you can do i

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

er hosting a public webpage has become > > unresponsive. The first time, all 300 available > > "https-jsse-nio-8443" threads were consumed, with the max age being > > around 45minutes, and all in a "S" status. This time all 300 were > > consumed in "S&quo

Re: Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 David, On 8/27/20 10:48, David wrote: > In the last two weeks I've had two occurrences where a single > CentOS 7 production server hosting a public webpage has become > unresponsive. The first time, all 300 available > "https-

Tomcat 9.0.29 - HTTPS threads age, max connections reached, Tomcat not responding on 8443

In the last two weeks I've had two occurrences where a single CentOS 7 production server hosting a public webpage has become unresponsive. The first time, all 300 available "https-jsse-nio-8443" threads were consumed, with the max age being around 45minutes, and all in a "

Re: Websocket semaphore lock on close() blocks all tomcat threads

On 14/07/2020 21:08, Mark Thomas wrote: > On 14/07/2020 20:57, Sridhar Rao wrote: >> >> We notice a behavior with tomcat where it becomes unresponsive and all >> http threads go into a timed wait state and the node becomes unresponsive. >> >> Tomcat Version: 8

Re: Websocket semaphore lock on close() blocks all tomcat threads

On 14/07/2020 20:57, Sridhar Rao wrote: > > We notice a behavior with tomcat where it becomes unresponsive and all > http threads go into a timed wait state and the node becomes unresponsive. > > Tomcat Version: 8.5.47 > Could this be a tomcat defect? Possibly. Let me ta

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

ackets in between that is marked as RED in wireshark. > > Okay, so far you have told us: > > 1. You are using Tomcat 8.5.29 >> [Raghav] yes correct. > 2. You have an with 450 threads in it >> [Raghav] Executor has 450 threads. > > 3. You see "lots of threads" &

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

ing Tomcat 8.5.29 [Raghav] yes correct. 2. You have an with 450 threads in it [Raghav] Executor has 450 threads. 3. You see "lots of threads" [Raghav] Yes above 450 threads or all the. 450 threads are alive. 4. You are seeing lots of RST packets. [Raghav]I can provide one sna

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

packets > in between that is marked as RED in wireshark. Okay, so far you have told us: 1. You are using Tomcat 8.5.29 2. You have an with 450 threads in it 3. You see "lots of threads" 4. You are seeing lots of RST packets We can't help you without more details. Pretend w

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

iman (rabhiman) wrote: > Yes you are correct apache tomcat version 8.5.29 being used. > > On 29/04/20, 7:22 PM, "Ragavendhiran Bhiman (rabhiman)" wrote: > > Hi Mark, > > We have configured 450 threads for port number 443 with the

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

On 29/04/2020 14:53, Ragavendhiran Bhiman (rabhiman) wrote: > Yes you are correct apache tomcat version 8.5.29 being used. > > On 29/04/20, 7:22 PM, "Ragavendhiran Bhiman (rabhiman)" > wrote: > > Hi Mark, > > We have configured 450 threads for

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

Yes you are correct apache tomcat version 8.5.29 being used. On 29/04/20, 7:22 PM, "Ragavendhiran Bhiman (rabhiman)" wrote: Hi Mark, We have configured 450 threads for port number 443 with the following executer I could see 450 threads open for ser

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

Hi Mark, We have configured 450 threads for port number 443 with the following executer I could see 450 threads open for servicing the clients in one specific setup only what could be the reason? Thanks a lot. Regards, Raghav On 29/04/20, 7:18

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

dor and version being used as well as OS. > Hi, > > I am seeing too many open threads to port number 443 with TLSv1.2, what could > be the primary reason for the same? Open threads? That doesn't make sense. Do you mean open ports, threads (idle, active, both) or something else?

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

Apache version 8.5.29 From: "Ragavendhiran Bhiman (rabhiman)" Date: Wednesday, 29 April 2020 at 6:50 PM To: "users-ow...@tomcat.apache.org" , "users@tomcat.apache.org" Subject: Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too ma

Re: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads

Adding tomcat users as well. From: "Ragavendhiran Bhiman (rabhiman)" Date: Wednesday, 29 April 2020 at 6:45 PM To: "users-ow...@tomcat.apache.org" Subject: Some questions regarding the TLS1.2 port 443 continuously communicating and too many open threads Hi, I am seeing t

Re: manager app, Complete Server Status, not shown list of NIO threads

, jvm 1.8.0_192-b12, Windows Server 2012 R2 and at Complete Server Status page I can see list of all http-nio threads and I can see a header of ajp-nio threads. But there is displayed only a label Max threads: and nothing more. In the localhost.log is an exception: 04-Dec-2018 10:31:38.109 SEVER

  1   2   3   4   5   6   7   8   9   10   >