Using HTTP 1.1 over a configured HTTP2 Connector

Dear Tomcat Team, I hope this message finds you well. I am currently facing a challenge regarding the use of HTTP/1.1 for specific API endpoints within a servlet configured for HTTP/2. My browser defaults to HTTP/2, which complicates the situation as I need to proxy some APIs to a server that

RE: Tomcat 10.1.30 and Many Timed Waiting threads

Chris, maxThreads has been set after reviewing the workload. We used a multiple of 64. The connections are from bots and are unlikely to be pipelined. Connections can be bursty - hence, a bigger acceptCount. Will revert to 10.0 and see. Regards, John -Original Message- From: Christo

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 moving to Tomc

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 with no c

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: [OT] accessing manager app

Michael, On 9/30/24 11:41, Michael Osipov wrote: Chris, On 2024/09/30 14:33:53 Christopher Schultz wrote: Michael, On 9/28/24 13:34, Michael Osipov wrote: On 2024/09/27 15:14:15 Christopher Schultz wrote: Sebastian, On 9/27/24 11:04, Sebastian Trost wrote: Francesco, On 26.09.2024 16:12,

RE: Tomcat 10.1.30 and Many Timed Waiting threads

Hi Chris, 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. Regards, John -Original Message- From: Christopher Schultz Sent: Monday, September 30, 2024 1:11 PM To: users@tomcat.apache.org Subject:

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-nio2-44

Re: accessing manager app

Chris, On 2024/09/30 14:33:53 Christopher Schultz wrote: > Michael, > > On 9/28/24 13:34, Michael Osipov wrote: > > On 2024/09/27 15:14:15 Christopher Schultz wrote: > >> Sebastian, > >> > >> On 9/27/24 11:04, Sebastian Trost wrote: > >>> Francesco, > >>> > >>> On 26.09.2024 16:12, Francesco Visc

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_WAITING on java.util.c

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 fine

Re: accessing manager app

Michael, On 9/28/24 13:34, Michael Osipov wrote: On 2024/09/27 15:14:15 Christopher Schultz wrote: Sebastian, On 9/27/24 11:04, Sebastian Trost wrote: Francesco, On 26.09.2024 16:12, Francesco Viscomi wrote: Hi all, I'm not able to understand why I cannot access to   http://localhost:8080/

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 Tom

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

Re: net::ERR_HTTP2_PROTOCOL_ERROR with 10.1.30

On 30/09/2024 07:38, Ahmed Ashour wrote: Hi all, Even though the regression should have been fixed in 10.1.30, our team still sees it around once weekly. Twice so far. With 10.1.29 it was very frequent, that the server can't be used, but with 10.1.30 it is much less, but sadly it seems on rare

Re: Setting Transfer-Encoding: chunked

On 30/09/2024 07:37, Lazar Kirchev wrote: Hello, Tomcat automatically adds header Transfer-Encoding: chunked if on http 1.1, the response code supports body and there is no Connection: Close header (Tomcat 9's code - https://github.com/apache/tomcat/blob/372f3cefe6225b58fcdae7c344d81396b8e08570/