Hi Mark, Thank you for the quick response. Please provide us a little more clarity on the 3rd query :
3. We see that RST is sent by tomcat on receiving http2 request, when does this happen ? >>> When things go wrong. E.g. when the client sends a request to a connection >>> that has been closed. Why does tomcat not send GOAWAY on connection close, upon next request from client it sends RST ? Also, Can you please send us the references to the timeout related fixes in 9.0.35 (since 9.0.22). Thanks and Regards Arshiya Shariff -----Original Message----- From: Mark Thomas <ma...@apache.org> Sent: Monday, May 18, 2020 4:17 PM To: users@tomcat.apache.org Subject: Re: RST on TCP level sent by Tomcat On 18/05/2020 11:01, Arshiya Shariff wrote: > Hi Team, > > Can you please help us with the below queries : There have been various timeout related fixes since 9.0.22. Please upgrade to 9.0.35 and re-test. > 1. When does a http2 connection close ? We see that the > keepAliveTimeout is > 20 seconds by default, but it is not closing the connection on > keepAliveTimeout. Please re-test with 9.0.35. > 2. How to keep the connections alive / How to enable ping frames to be > sent to the other end to keep the connection alive ? There is no standard API to send an HTTP/2 ping. If you want to keep the connections alive for longer, use a longer keep-alive setting. > 3. We see that RST is sent by tomcat on receiving http2 request, when > does this happen ? When things go wrong. E.g. when the client sends a request to a connection that has been closed. > 4. What are the recommended ipv4.tcp settings for these kind of scenarios ? There are no recommended settings. Mark > > > > Embedded Tomcat : 9.0.22 > > Java Version : 1.8.0.201 > > Hardware : Red Hat Enterprise Linux Server release > 7.4 > > > > Thanks and Regards > > Arshiya Shariff > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
