When the web browser clocking issue happens, the web browser will just clock when I click on a link in this application and then eventually time out on the browser side. The TCP connections mentioned in original posting represent this web browser click that clocked and eventually timed out at the browser. The Spring Boot trace is showing that the https request are making it to the server side socket and nio-exec threads are starting to act on it. There are several nio-exec threads doing a read register on the socket (within the same millisecond), but then nothing else happens with the socket. There is no nio-exec write register or reading/processing https data from the socket. After 60 seconds, the connections are closed due to the server.tomcat.keep-alive-timeout default setting.
-----Original Message----- From: Mark Thomas <ma...@apache.org> Sent: Thursday, August 15, 2024 9:35 AM To: users@tomcat.apache.org Subject: Re: Web browser clocking issue at Apache Tomcat 10.1.20 on Linux [You don't often get email from ma...@apache.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] [External] On 15/08/2024 14:36, Tim Zielke wrote: <snip/> > web browser clocking issues <snip/> Can you clarify what you mean by this please. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
