The issue still persists with 11.0.5.
Thanks,Ahmed
On Friday, March 7, 2025 at 11:20:18 AM GMT+1, Boris Petrov
wrote:
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
That's unfortunate. I haven't hit the issue in 9.0.102 but who knows -
it just might be even rarer...
On 3/11/25 11:41 AM, Ahmed Ashour wrote:
The issue still persists with 11.0.5.
Thanks,Ahmed
On Friday, March 7, 2025 at 11:20:18 AM GMT+1, Boris Petrov
wrote:
I've been doing that
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
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
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
On 17/01/2025 15:31, Boris Petrov wrote:
Hi Mark,
I'm not sure what you mean that the error is being reported client-side.
It is, yes, but the backend itself returns status 500 - so I guess
that's the reason Chrome gives net::ERR_HTTP2_PROTOCOL_ERROR. Or who
knows, I'm not sure.
A 500 respo
Hi Mark,
I'm not sure what you mean that the error is being reported client-side.
It is, yes, but the backend itself returns status 500 - so I guess
that's the reason Chrome gives net::ERR_HTTP2_PROTOCOL_ERROR. Or who
knows, I'm not sure. The relevant part from the log that I sent:
16:54:07.
On 16/12/2024 10:44, Mark Thomas wrote:
On 16/12/2024 10:28, Boris Petrov wrote:
Hi Mark,
Thanks for the response and sorry for the delayed answer.
I don't think my use case is special in any way. It's just a normal
web- app exposing a JSON REST API that is being queried from time to
time. I
On 16/12/2024 10:28, Boris Petrov wrote:
Hi Mark,
Thanks for the response and sorry for the delayed answer.
I don't think my use case is special in any way. It's just a normal web-
app exposing a JSON REST API that is being queried from time to time.
I'm hitting the issue with just a normal u
Hi Mark,
Thanks for the response and sorry for the delayed answer.
I don't think my use case is special in any way. It's just a normal
web-app exposing a JSON REST API that is being queried from time to
time. I'm hitting the issue with just a normal usage, not by
stress-testing or anything. T
On 10/12/2024 08:28, Boris Petrov wrote:
I've been trying all versions of Tomcat since 9.0.93 (including the
newly released 9.0.98) and all of them have the same issue. I find it
extremely strange that no-one else hits this.
It sounds like the issue is timing related. These can be very sensiti
I've been trying all versions of Tomcat since 9.0.93 (including the
newly released 9.0.98) and all of them have the same issue. I find it
extremely strange that no-one else hits this.
Mark, are you still looking into this problem? You mentioned that you
have some suspicions. I can't give you a
On 09/10/2024 03:33, Boris Petrov wrote:
I also have been experiencing the same issue (with Tomcat 9). 9.0.93
works fine. 9.0.94 is unusable. 9.0.95 and now 9.0.96 almost work but
sometimes I get the same behavior as with 9.0.94. I see it in my
integration tests - there are some sporadic failur
I also have been experiencing the same issue (with Tomcat 9). 9.0.93
works fine. 9.0.94 is unusable. 9.0.95 and now 9.0.96 almost work but
sometimes I get the same behavior as with 9.0.94. I see it in my
integration tests - there are some sporadic failures here and there when
I upgrade from 9.0
> How rare? Once in how many requests? Can you trigger this via automatedÂ
> testing e.g. with wrk?
After working for some time (from 10 minutes to an hour), making a request to a
page (with subsequent JS/images) every one minute, the issue is shown, happens
on Chrome and Brave.
The requests wi
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
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 occasions to occur.
I understand the diffi
17 matches
Mail list logo
