On 24/09/2024 12:40, Thomas Meyer wrote:
Am 24. September 2024 10:44:46 MESZ schrieb Mark Thomas <ma...@apache.org>:
On 24/09/2024 08:59, Thomas Meyer wrote:
Hi,
We see sometimes elapsed time values with over 100 million milliseconds and
status code 500 in the Tomcat logs for HTTP/2.0 connections.
Is that expected or a bug?
Is it just the large elapsed times that are unexpected or are the 500 status
codes unexpected as well?
Mhh, now that you mention it, I think I would have expected a 200 return code
for this request, which actually took 113 seconds what I can see from the logs,
but the frontend has a timeout of 60 seconds, so the request was probably
aborted by the frontend.
So there might be an issue with elapsed time when we receive a stream
reset from the client. I'll take a look at the code.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
