Re: Tomcat 9.0.98 Performance hits AWS 100% CPU

2025-03-07 Thread Christopher Schultz
Chuck, On 3/7/25 5:38 PM, Chuck Caldarale wrote: On 2025 Mar 7, at 16:06, Timothy Resh wrote: Dear Apache Support Team, I'm running Tomcat 9.0.98 in the AWS Cloud. After several days of use, we see that the CPU utilization eventually reaches 100% in the Cloud, but when we RDP into the Serve

Re: Tomcat 9.0.98 Performance hits AWS 100% CPU

2025-03-07 Thread Chuck Caldarale
> On 2025 Mar 7, at 16:06, Timothy Resh wrote: > > Dear Apache Support Team, > > I'm running Tomcat 9.0.98 in the AWS Cloud. After several days of use, we > see that the CPU utilization eventually reaches 100% in the Cloud, but when > we RDP into the Server and look at the Task Manager, we do

Tomcat 9.0.98 Performance hits AWS 100% CPU

2025-03-07 Thread Timothy Resh
Dear Apache Support Team, I'm running Tomcat 9.0.98 in the AWS Cloud. After several days of use, we see that the CPU utilization eventually reaches 100% in the Cloud, but when we RDP into the Server and look at the Task Manager, we do not see the performance being impacted. However, users complain

Re: net::ERR_HTTP2_PROTOCOL_ERROR with 10.1.30

2025-03-07 Thread Boris Petrov
I've been doing that for the past few hours. For now all looks good. I'll write here if I still see the problem - so hopefully you don't hear from me today! :D Thanks again! Regards, Boris On 3/7/25 12:14 PM, Mark Thomas wrote: On 07/03/2025 09:00, Boris Petrov wrote: Hi Mark, I'm looking

Re: net::ERR_HTTP2_PROTOCOL_ERROR with 10.1.30

2025-03-07 Thread Mark Thomas
On 07/03/2025 09:00, Boris Petrov wrote: Hi Mark, I'm looking at the 9.0.101 release notes and see this: Fix a race condition in the handling of HTTP/2 stream reset that could cause unexpected 500 responses. Could that be the same issue as this thread here and do you think it might have been

Re: net::ERR_HTTP2_PROTOCOL_ERROR with 10.1.30

2025-03-07 Thread Boris Petrov
Hi Mark, I'm looking at the 9.0.101 release notes and see this: Fix a race condition in the handling of HTTP/2 stream reset that could cause unexpected 500 responses. Could that be the same issue as this thread here and do you think it might have been resolved with that specific fix? As alw