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.

>
>If the 500s are expected (or at least explainable) it is possible the elapsed 
>time calculation isn't right for some error conditions.
>
>Mark
>
>
>> 
>> I assume this is because of http2 multiplexing maybe?
>> 
>> Tomcat version is 10.1.30
>> 
>> Mfg
>> Thomas
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>For additional commands, e-mail: users-h...@tomcat.apache.org
>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Reply via email to